4. Issue Management with AccuWork™
4. Issue Management with
AccuWork™
The AccuWork experience includes setting up an issues database format (“schema”), creating issue records, querying the issues database, and using the “change package” integration between configuration management and issue management.
Setting up the Default Schema
The first step is identifying the schema you want AccuWork to use to record issues. You can create your own, but let’s use the default schema to get started.
1.
Select Admin > Schema Editor from the AccuRev main menu.
2.
If necessary, select your depot from a list of depots in a pop-up window and click Ok.
3.
Click Yes (“Do you want to use the default schema?”).
4.
Click Ok (“Please note …”).
5.
Click Save (lower right-corner of Schema Editor tab).
Creating a Few New Issues
Once the AccuWork schema has been set up, you are ready to submit issues for enhancements and any bugs you find.
1.
Click the Create Issue button () on the AccuRev main toolbar.
Alternative: Select Issues > Create Issue from the AccuRev main menu.
2.
Enter data in all of the required fields (red labels).
3.
Experiment with how the different types of fields manage various types of data.
4.
Click the Save and Close button () to save the issue record and close the tab.
5.
Repeat this process a few times if you have more issues you report.
Creating a Query
1.
Click the View Issue Queries button () on the AccuRev main toolbar.
Alternative: Select Issues > View Issue Queries from the AccuRev main menu.
2.
If necessary, select your depot from the list of depots and click Ok.
The AccuWork Queries tab appears; the name of the depot you selected in the previous step is displayed in the tab.
3.
Click the New Query button () to create an empty new query.
4.
In the Edit Query dialog box, click Click here to add….
5.
Set the first choice box value to issueNum.
6.
Set the second choice box value to greater than or equal to.
7.
Enter the number 1 in the third query box.
8.
Click Ok.
The results of the query are displayed in the Query Results pane, on the right side of the Query tab.
You might decide that you want to display more information about the issues that your query returns. Add more fields now.
9.
Click the Set up Columns button () in the Query Results pane.
10.
Select additional fields to appear in the Query Results pane:
a.
Select a field from the Available list (shortDescription, for example).
b.
Click the right-arrow button () to move the field to the Selected list.
c.
Repeat the steps above for all of the fields you wish to add to the query results output.
d.
Click Ok.
11.
Give your query a name by clicking its name "New Query 1" twice (with a short pause in between) and then typing the name (for example, All Defects).
The name of the new query appears in the left (Query List) pane, which lists all the queries that you have created.
12.
Click the Save button () above the Query List pane to save your query.
Making a Query Your Default Query
If you want, you can designate any query as your default query. When you do, AccuRev runs this query automatically when you open the query tab.
1.
In the Query List pane, right-click the query you just created and select Set as Default from the context menu.
2.
Close the query tab.
3.
Click the View Issue Queries button () on the AccuRev main toolbar.
Alternative: Select Issues > View Issue Queries from the AccuRev main menu.
The query you just created runs automatically, because you set it as your default query.
Enabling the Built-in Integration Between AccuRev Configuration Management and AccuWork Issue Management
1.
Select Admin > Schema Editor from the AccuRev main menu (or return to the existing Schema Editor tab).
2.
If necessary, select your depot from the list of depots and click Ok.
3.
Go to the Change Packages tab.
4.
In the Change Package Results section (top part), click the Setup Columns button ().
5.
Select some fields from the Available list (Example: issueNum, shortDescription), and click the right-arrow button () to move the fields to the Selected list.
6.
Click Ok.
7.
In the Change Package Triggers section (bottom part), click New Trigger button () in the toolbar.
A new window opens, in which you specify a condition, along with a query to be performed if that condition is satisfied when the integration is invoked.
8.
In the Condition section (top part), click Click here to add….
9.
Use the three choice boxes to form this condition (where <depot> is the name of your depot):
PROMOTE_DEST_STREAM is in hierarchy <depot>
10.
In the Query section (bottom part), click Click here to add….
11.
Use the choice boxes and the text field to form this condition:
issueNum greater than 0
This query selects all issue records.
12.
Click Ok.
13.
Click Save (lower right-corner of Schema Editor tab).
14.
Open a workspace (or go to one that is already open).
15.
Edit and Keep several files.
16.
Promote all those files.
The integration evaluates the condition you defined in Step 8 (it is TRUE), then runs the query you defined in Step10. The selected records are presented as a list of issues to choose from.
17.
Select the issue that you want to associate the promoted files with, and click Promote.
18.
Click the Open Issue button () on the AccuRev main toolbar.
Alternative: Select Issues > Open Issue from the AccuRev main menu.
19.
Enter the number of the issue you chose when prompted (Step 17), and click Ok.
The issue appears in a new tab.
20.
Go to the Changes tab.
The files that you promoted are listed on this tab. The specific versions that you promoted are listed in the Version column.
Turning Off the Integration Between Configuration Management and Issue Management
1.
Select Admin > Schema Editor from the AccuRev main menu (or return to the existing Schema Editor tab)
2.
If necessary, select your depot from the list of depots and click Ok.
3.
In the Change Packages tab, locate the condition/query pair you created in the Change Package Triggers section and select it.
4.
Click the Delete Trigger button ().
5.
Click Save (lower right-corner of Schema Editor tab).
With no query to be invoked at Promote time, the integration is effectively disabled.
Borland