The AccuWork Edit Form tab provides a familiar, easy-to-use interface for creating new issue records and modifying the contents of existing issue records. The edit form also provides access to an issue record's
change package.
To create a new issue record, choose Issues > New Issue from the GUI main menu, or click the

button in the GUI main toolbar.
To modify an existing issue record, choose Issues > Look Up from the GUI main menu, or click the

button in the GUI main toolbar.

If you have implemented third-party issue tracking system (ITS) keys in your AccuWork schema, this dialog box displays a pair of radio buttons that let you indicate whether you want to use AccuWork issue numbers or third-party ITS keys when looking up issues. See the “Using Third-Party ITS Keys” chapter of the AccuRev
Technical Notes for more information.
A typical AccuRev repository contains multiple
depots. Each depot can have its own AccuWork configuration. In each depot, the issue records are numbered sequentially: 1, 2, 3, ... The
New Issue or
Look Up command applies to the
current depot.
AccuWork can be configured to use a lookup field other than the default (field name issueNum, field label
Issue). In this case, the label for the configured field appears in the prompt window, and you must enter a value that exactly matches (except for uppercase/lowercase) some issue record's value of that field.
·
|
The Changes subtab displays the issue record's change package, and provides commands for analyzing and manipulating the change package's entries.
|
·
|
The Issue History subtab displays a complete breakdown of how the issue record's field values have changed over time.
|
AccuRev Workflow is documented in the AccuRev® Web Interface User’s Guide, Version 2012.1 or later, but a brief summary of this toolbar is:
Note: If an issue doesn't match any workflow stages, or is subject to multiple workflows, AccuRev displays a message to that effect where the buttons would otherwise appear. If an issue's fields don't match with the logic specified for a transition, the transition button appears, but it is grayed out until the user changes the fields required to bring the issue into compliance.
You can enter and change values in any number of fields, and visit different pages in a multiple-page form. Here are some notes, describing aspects of AccuWork edit forms that may differ from other fill-in-the-blanks forms:
To move from field to field, use the mouse or press Tab and
Shift-Tab. To move from page to page in a multiple-page edit form, click the subtab name (there is no keyboard accelerator).
The Enter key confirms a menu choice or enters a line-break in a multiple-line text field. It does not perform field navigation. Within a multiple-line text field, the
Tab key inserts a
TAB character, rather than jumping to the next field.
This makes it easy to view a set of consecutive issue records. If you’ve made some changes that you haven't yet saved, AccuWork prompts you to save or discard those changes before switching to the previous or next one.
If a field's label appears in red, it is a required field. You cannot
Save the issue record until every required field has a
value. (A text field has a value if it's non-empty. A multiple-choice listbox field has a value it it's not “<none selected>”.) Some of those fields may have gotten their values through an automated field initialization.
Field initializations and required fields are implemented through AccuWork's field validations (or "edit checks") facility. As you work in an edit form, changing field values, you may notice these field-validation effects:
Your entries in an edit form are not stored in the issue record until you click the
Save or
Save & Close button in the edit form toolbar. If you don't wish to save your work, just close the edit-form tab as you would any GUI tab.
•
|
If you clicked Save, the edit form tab remains open, with the newly assigned issue number replacing the "New Issue" label and appearing in the Issue field.
|
You can fill in the individual subfields manually, or use the
Select Date button to display choices ("tomorrow", "2 days ago", etc.) that fill in the subfields automatically. Once these subfields are filled in, you can revise them individually or by clicking the
Select Date button again.
When you use the form you can use the
control at the top of the textbox to temporarily expand the height. Click the control again (it's now

) to contract the height. A scroll bar appears on the textbox whenever the current contents of the field are not completely visible.
A log field is a variant of a multiple-line text field. You can type directly into such a field. And if you click the
Add Timestamped Text control, a timestamp text line is inserted at the beginning or end of the field.
An edit form can contain one or more attachment fields. In each such field, you can specify one or more files and/or Internet addresses (URLs) to be attached to the current issue record. AccuWork displays the attachments data as a table.
In addition to specifying the location of a file or Internet resource, you enter a name and optional comment. AccuWork automatically fills in your username, the date, and the size of the attached file. (Internet URLs are assigned a size of 0.) If the edit-form field is not large enough to show all these attachment parameters, use the scroll bar to see all the data. You can also resize and rearrange the columns of an attachments table.
·
|
Duplicate: You can specify that issue record B duplicates issue record A, so that no work need be done on B. (Perhaps the same bug was reported twice.) Any number of records (B, C, D, ...) can duplicate a given record (A). The default AccuWork issue schema requires that a Duplicate relationship be established when an issue record's State field is set to the value Duplicate.
|
·
|
Dependency: You can specify that issue record B depends on issue record A (for example, from a project management viewpoint). AccuRev imposes no further semantics on such dependencies; this is a good application for user-defined scripts or practices.
|
IMPORTANT NOTE: This relationship is independent of
change package dependency relationships among issue records, which are maintained automatically by AccuRev.
·
|
Subtask: You can specify that issue record B defines a subtask of the work to be performed for issue record A. In this case, AccuRev considers issue record A to be "in" a particular stream only if issue record B is "in" that stream, also.
|
Issue record relationships can be viewed only in the AccuWork GUI. The edit-form tables that display issue relationships are not included when you export an issue record (for viewing or printing). These tables are not included when you use the AccuWork command line interface (CLI) to dump the contents of an issue record. (see the
AccuWork™ Command-Line Interface chapter in the AccuRev
CLI User’s Guide.)
When you create or delete a relationship between issue records, the change to both issue records is saved immediately. There is no need to invoke the
Save command on the issue record.(The
Save button is not enabled in the edit-form toolbar.)
On the other hand, "A duplicates B" is the same as "B is duplicated by A". This means that when you add an entry to the
top table of one issue record, AccuWork automatically adds it to the
bottom table of the other issue record (and vice-versa).
•
|
There is a State field in the header section, one of whose values is Duplicate. (The Status value must be Closed to enable the setting of the State value to Duplicate.)
|
•
|
An edit-form validation specifies that when you set the State field's value to Duplicate, you must indicate which issue record is duplicated, by creating an entry in the Duplicates field.
|
At any time when you're using an edit form, you can print the issue record. For AccuWork, printing means "publish to the Web" -- which means either "create an HTML file" or "create an XML file".
1.
|
Click the Export button in the form's toolbar. 
|
When creating an HTML file, AccuWork outputs all the content of the issue record and approximates the form layout, too. Even if the edit form has multiple pages, you need to "print" only once. All of the pages are combined into a single HTML or XML file:]

On Windows machines, AccuWork automatically invokes a web browser on the HTML file it creates. If you wish, resize the browser window to optimize the look of the issue record. HTML documents automatically adjust to changes in window width. Then, use the browser's print command to create a printout of the issue record.