Edit issues to provide additional or updated information.
Tip: If you need to update field values for multiple issues, use bulk field changes. This allows you to quickly update multiple items simultaneously. See Updating Multiple Items.
1. In the Issues list window, select the issue and click Edit. You can also choose Edit > Edit.
The Edit Issue
Note: Icons may indicate the item is locked or marked as suspect. See About item status indicators.
2. Make any changes to the general fields in the top part of the Edit Issue dialog box.
3. Make any changes to information on the tabs in the details area.
|Detail||Users who reported the issue and other information, such as a detailed description, steps to reproduce the issue, the computer configuration the issue was found on, and file attachments.||Adding issues|
|Custom Fields||Custom fields used in the project. These are unique fields your team uses to capture additional information.|
|Workflow||Work performed on the issue as it moves through the workflow.||Viewing workflow event history|
|Workaround||How to work around the issue until it is fixed or implemented.|
|Source Files||Files attached to the issue from source control applications, such as Surround SCM.||Working with source files|
|Email sent about the issue. You can reply to email. Available only if email tracking is enabled for the project.||Viewing email and Replying to email|
|Links||Items linked to the issue. You can add, edit, delete, and diagram links, mark linked items as suspect to indicate they may be impacted by changes, and clear or investigate suspect dependencies.||Working with item links|
|Folders||Folders the issue is included in. You can add the issue to other folders, move it to different folders, or remove it from folders. You cannot add or move the issue to public folders you do not have permission to modify or are locked, or locked private folders. You cannot remove the issue from locked folders.||Organizing Items with Folders|
|History||Historical information about the issue, such as when it was created, when it was last modified, and all actions performed on it.||Viewing Item History|
4. Click Create Test Case to create a test case based on the issue. See Creating test cases from issues.
5. Click Create Requirement to create a requirement based on the issue. See Creating requirements from issues.
6. Click Send Email to email a user about the issue. See Emailing from Helix ALM.
7. Click Watch to be notified every time the issue changes. See Watching issues to be notified about changes.
8. Save the issue.
OKto save and close the issue.
- Click Apply to save and continue working on the issue.
Tip: If the changes impact linked or related items, you may want to mark the items as suspect. This flags the items to indicate they should be reviewed. See Marking items as suspect.