6.4. View Issue Details page
This page displays complete information about an Issue.
Most of the fields are self-explanatory. Assigned To indicates the developer handling the Issue. Priority is fully functional but currently does nothing of importance.
In the main section's footer, just below the fields list, is a set of action buttons that a user can leverage to work on the Issue.
Edit - brings up a page to edit all aspects of the Issue.
Assign to - in conjunction with the dropdown list next to the button, provides a shortcut to change an Issue's assignment.
Change Status to - in conjunction with the dropdown list next to the button, allows changing the status of an Issue. This will redirect another page allowing the user to add notes or change relevant information (see
Section 6.5, “Issue Change Status page”).
Monitor / End Monitoring - allows users to subscribe to an Issue; they will receive email notifications whenever it is updated.
Users who reported or are assigned to the issue typically do not need to monitor it to receive the notifications, because they get them by default unless the administrator changed the configuration.
Stick / Unstick - Changes the Issue's
sticky status. Sticky Issues are listed at the top of the first page in the Issues list (see
Section 6.3, “View Issues page”), unless this has been disabled by filter settings.
The sticky status can also be changed using the Set/Unset Sticky group action.
Clone - create a copy of the current Issue. This presents the user with a new Issue reporting form, prefilled with all the information from current Issue. Upon submission, a new Issue will be created, with an optional relationship to the current one.
Reopen Issue - Allows a user having the appropriate access level to re-open a resolved or closed Issue. This will redirect another page allowing the user to add notes to explain the re-opening reason (see
Section 6.5, “Issue Change Status page”). The issue will automatically be put into Feedback status.
Close - Changes the Issue's status to Closed.
Depending on configuration, authorized users may be able to close issues without having to resolve them first, or may only be allowed to close resolved issues. This will redirect another page allowing the user to add notes or change relevant information (see
Section 6.5, “Issue Change Status page”).
Move Issue - Lets the user move the Issue to another project.
Delete Issue - Allows authorized users (see
$g_delete_bug_threshold in
Section 5.24, “Misc”) to permanently delete the Issue. A dialog will prompt the user confirm the operation.
It is generally not recommended to delete issues, unless it is frivolous, test or completely off-topic. Instead, resolve the Issue with an appropriate Resolution code (see $g_resolution_enum_string in).
Another section is provided to view, add and delete relationships. The following types are available:
related to - horizontal relationship. This is a regular link between two Issues, without any particular meaning.
parent / child - hierarchical relationship. The user is warned about resolving a parent Issue before all of its children are resolved.
duplicate of / has duplicate - hierarchical relationship. An Issue marked as duplicate of another one is generally resolved with duplicate resolution.
Below this, there will be a form allowing to add notes and/or file attachments. Issue notes are shown in a separate section further down the page.
If enabled, a Time Tracking section will report the time spent on the Issue.
Finally, the History section will show a chronological audit trail of all activity on the Issue.
Which Fields, buttons and Sections are displayed depends on system configuration and the user's access level. Additional sections may be inserted by Plugins.
