The Issue Edit Form
The Issue Edit form is used to create, view, and edit issue records (AccuWork) A data record, consisting of values of data fields, stored in an issue database.in an AccuWork issue database (AccuWork) A set of issue records, each of which implements a bug report, feature description, etc. Each depot can have its own issue database. Each issue database has its own schema.. To access the form, use one of the following methods:
Click the 
New Issue button in the Web GUI toolbar and choose a depot.
Click the 
Look up Issue button in the Web GUI toolbar, choose a depot, and enter an issue number.
Double-click an issue in the Query Results pane, or select the issue and choose Open Issue from the context menu.
Choose the Open Issue command from the context menu whenever a list of issues is shown.
Note: The contents and layout of the Issue Edit form are set up using the AccuRev Schema Editor. The Schema Editor (accessible from the AccuRev GUI) is used to define an AccuWork issue database and an Issue Edit form. Each depot The portion of the AccuRev repository that stores the entire history of a particular directory tree. See element, version. can contain one issue database.
Although each issue database has its own Issue Edit form, all Issue Edit forms have these features in common:
The Issue Edit form consists of one or more pages, which appear as subtabs within the overall issue tab.
Every Issue Edit form has two special subtabs:
The Changes subtab displays the issue record's change package A set of entries, each in the form of a basis-version/head-version pair, recorded on the Changes tab of an issue record. The change package records the changes to one or more elements, made to implement the feature or bugfix described in that issue record. Each entry in the change package describes changes to one element: the changes between the basis version and the head version. See patch., and provides commands for analyzing and manipulating the change package's entries.
The Issue History subtab displays a details of how the issue record's field values have changed over time.
Typically, there is a header section, which always remains visible as you switch from page to page, using the mouse.
Each field in the issue database is shown with a descriptive text label to its left. (By default, a label in red text indicates a required field.)
Every Issue Edit form contains a toolbar with issue-related commands.
You can enter and change values in any number of fields, and visit different pages in a multiple-page form. To move from field to field or page to page, use the mouse or press Tab and Shift-Tab. To select a page, press Enter. The Enter key also confirms a menu choice or enters a linebreak in a multiple-line text field.
The Issue Toolbar contains a set of controls used to navigate among issues. If you open an issue from the Query Results pane or other list of issues, these navigation icons will navigate among issues in the list. If you open an issue using the Look up Issue command, the navigation icons will navigate among all issues in the database.
First Issue
Display the first issue from the query results. This icon is disabled when not accessing query results.
Previous Issue
Display the previous issue.
Next Issue
Display the next issue.
Last Issue
Display the last issue from the query results. This icon is disabled when not accessing query results.
The field to the right of the navigation controls () displays which issue in the set is currently displayed, and how many issues there are in the set being navigated through.
If you navigate away from an issue using these controls after having made changes to it, the Web GUI will prompt you to save your changes.
AccuWork supports field initializations and required fields by implementing the validation rules set up in the Schema Editor (accessible from the AccuRev GUI). As you work in an Issue Edit form, you may notice these effects:
A new issue has values automatically filled in for certain fields.
One or more field have automatically been set to a specified value.
The set of choices available in a list has changed.
The set of required fields has changed. 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 (i.e., is not empty or in the case of lists, is set to a value other than <none selected>). Some required fields may have values set through an automated field initialization.
The Changes tab has become required. This validation option prevents an issue from being saved unless there are versions associated with the issue.
One or more fields, tabs, or issues are read-only (no edits can be made).
Setting a field to a certain value (e.g., setting State to Duplicate) requires a type of relationship to another issue (e.g., indicating which issue this one is a duplicate of).
If you attempt to save the issue record when one or more required fields lack a value, a dialog containing a list of the required fields displays. You will not be able to save the issue record until values for each of these fields have been set.
Some text fields can have multiple lines, as well as a default height and width on the Issue Edit form. These dimensions are set when the field and the form are designed in the Schema Editor.
Click the control at the top of the multiple-line text field to temporarily expand it. Click the control again to contract it. 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. If you click the 
Add Timestamped Text control, a timestamp line (containing your username and the current date and time) is inserted at the end of the field.
Note that when working with fields containing lists of AccuRev users on an issue form, only active users are typically displayed. Occasionally, a user who has been deactivated in AccuRev is still assocated with an issue (as the submitter of the issue, for example). In this case, the user's name is added to the list of users displayed in user fields for that issue.
Date fields in AccuWork issues have an associated date/time control to assist in filling in the field. Click in the field to display the date/time control. This control defaults to the current date and time. Use the navigation arrows (<< and >>) to pick a different month. Click a day or adjust the time to put the date and time in the field. To close the control, use the click-to-close icon (
)
To clear an existing value from the date field, click the Clear button to the right of the field
AccuRev supports four types of relationships used to link issues: dependencies, duplicates, subtasks, and tracking issues. Depending on the settings in the Schema Editor, these relationship fields may appear on the Issue Edit form. The example below shows a subtask relationship field on the Issue Edit form.
Use the 
Link issue command to add a link to an existing issue. This command displays a dialog to choose the relationship type and enter the issue number for the issue being linked to. This command is not available before the issue has been saved.
The linked issue displays in the relationship field. Use the 
Remove link command to remove the relationship between the current issue and the selected link.
An Issue 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 an optional comment. AccuWork automatically fills in your username, the date, and the size of the attached file. (URLs are assigned a size of 0.)
An attachment field includes its own toolbar, with these buttons:
New Attachment
Define a new file attachment for this issue record. An Add Attachment dialog appears, in which you can specify a file to attach and a comment string.
New URL
Define a new attachment to be the address (URL) of an Internet resource. A New URL dialog appears, in which you specify a URL and a comment string. AccuWork automatically inserts http:// in the URL field. You can erase this if you want to specify a location accessed by another Internet protocol.
Open Attachment
Open the selected attachment. Opening a file uses the browser's file type associations to open the file using the correct program. If the file cannot be opened within the browser, you are prompted to open the file using an external program, or save the file to disk.
Save Attachment As
Create a copy of the selected file attachment on the client machine. URL attachments cannot be saved in this way.
Delete Attachment
Remove the attachment from the issue record (and from the depot). A URL attachment can be deleted at any time. A newly added file attachment can be deleted if you haven't yet saved the issue record.
When you save the issue record, each file is copied to the depot, so that the data always remains available through the issue record, even if an original file is deleted.
Your changes to an issue in the Issue Edit form are not saved until you click the 
Save button in the tab's toolbar. When you save an issue record, the issue record is stored in the depot's issue database, within the repository. A transaction of type dispatch records the modification of the issue record. No matter how the issue record is modified subsequently, you can see the record of changes to it on the Issue History subtab. For new issues, AccuWork assigns the next available integer issue number to the new issue record when you save your work. This number cannot be modified.
If you attempt to close the Issue Edit form without saving, the Web GUI prompts you to save your changes. If you don't wish to save your work, just choose Close.
You are also prompted to save if you attempt to navigate away from a changed issue.
If the issue you are working on has been edited and saved by another user during the time you are making changes, the Web GUI notifies you when you attempt to save.
Both a mailto link and a hypertext link to the issue are shown at the top of the Issue Edit form.
The mailto link () opens a new email message (using your system's default email application) when you click it. The body of the email contains the issue URL. Recipients can click the link (after logging in to the Web GUI) and view that issue.
The hypertext link contains the same information as the mailto link, in a form useful for bookmarking or distributing. For security reasons, navigating to a bookmark saved from AccuRev will cause the Login dialog to appear if you are not logged in. After you log in, the URL's contents appear immediately in your browser.