|
Updating Issues
Alcea Fast BugTrack has been designed to be unrestrictive, by default. Thus, priority, Status and AssignedTo fields can be changed at any time. This allows flexibility by assuming that users can follow a process without needing restrictions. However, if the administrator chooses, some states and users may not be available due to restrictions that they have set up. Please check with the administrator for the correct process if you notice that you can not see some users or states.
Fields are divided into sections such as the Info, Details and the History Trail. All editable fields are located in the Details section. In some cases the detail fields can also be set up as read only by the administrator.
Notes:
- - Fast BugTrack can keep a history of all changes or just relevant ones (default). Ask your admin if you want this option for your system.
- - A suppress Notification checkbox is available beside the save button for cases where notification is not necessary.
- - After an update, the results page has a summary of exactly who was sent a notification. Users are placed in the skipped list if their address was found more than once, or if the system determines that a person is assigning to themself.
Working with Attachments
The Add Attachment link will open a pop up window where an attachment can be added through a browse menu. Attachments can be of any file type - Images, Documents, Zip files, etc. After submitting an attachment, you can attach another file, or close the popup to finish editing the issue. Attachments are viewed by selecting the filename, or the comment may be edited by selecting "Edit".
If an attachment is added, it will not be seen on the previous edit page until its details are submitted or the entire page is refreshed. However, if you refresh the page, all of the form elements get reset and the edit starts from scratch.
Bulk Assignment / Archiving Bugs
The "Bulk Update" link is available to admin users for updating multiple fields. This menu shows a list of issues with checkboxes and then a field list with checkboxes. Changes require a check for each issue that needs updating and each field that is to be changed in the bulk update.
This feature can be handy if you need to pass several issues between users, or change the status of a long list of issues.
If you would like to archive bugs (so that they are no longer visible within Fast BugTrack), select the appropriate bugs, and press the archive button.
Notes:
Due to the power of Bulk Update feature, notification is suppressed by default for this feature. If you would like the notification to run as normal, simply uncheck the suppress notification checkbox, next to the Save button.
A cloning feature has been added to this page to allow you to create new bugs where fields default to the values of the issue they are being cloned from. The Clear Original History blanks out the history for the new cloned issue, rather than keeping the parents entries. The Record Cloning History simply places a cloned from note in the description.
|