Updating Issues

Alcea FIT has been designed to be unrestrictive, by default. This default flexibility assumes that users can follow a process without needing restrictions. Thus, priority, Status and AssignedTo fields can be changed at any time, unless the administrator defines workflow rules to control them.

Fields are divided into sections such as the Info, Details and the History Trail. These sections define a set of related fields that have been configured for your system.

You can see a complete history of the issue in the history section on the bottom of the page. The following history options are available: Default - the original history type from older version where only fields that were historical types are shown. Traceback - a complete traceback of data for all fields. Quick - a quick compact one line history listing.

Quick+Traceback - this option gives the quick history line summary followed by all modification for every change made to an issue Detailed Traceback - this option gives a full history traceback with color coded formatting of previous and current values listed for every change.

Notes:

- 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. Attachments are viewed by selecting the filename from the attachment field listing. The attachment can be deleted or the comment may be edited by selecting the "Edit" link for the attachment.

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 FIT), select the appropriate bugs, and press the archive button. This option effectively removes them from the system, but leaves a trace of them in case they are ever needed again.

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.