Front End Issue Detail Screen

The front end issue display can like all of the front end screens be modified to have a 'specific' 'look and feel'. Two examples are illustrated in this section.

Figure 4.54. Front End Issue Detail

Front End Issue Detail

Below is an alternative image of the issue display screen using some supplied CSS code, and also illustrating the display where there is an associated attachment. If there is more than one attachment the list within the attachment section will be slightly longer.

Figure 4.55. Front End Issue Detail (2)

Front End Issue Detail (2)

The front end issue display is also configurable, just as the issue display is configurable to determine which fields are displayed. There are separate options for Issues displayed from the menu, and those displayed from a link from the main issues list display.

[Note]Note

Progress History may or may not be displayed depending upon the configuration settings. Even within the progress records themselves each record may be individually configured to be displayed or not, and even to whom it may be displayed based upon the access group of the user and that of the progress record.

[Note]Note

If there are any attachments for the displayed issue, then an additional grid will be shown with the attachment details.

[Note]Note

If the issue displayed does not have any resolution provided, i.e. the issue is still open or in progress, then the 'Resolution' information will not be displayed in Release 1.6.0 or later.

Custom fields may also be present and displayed if they are configured for the specific project to which the issue is attached.

The print and email (which send a page link to the recipients) icons are also optional. The display of the audit details for the record is optional, and is set in the Menu settings.

If the person viewing the issue detail is logged in (or an issue administrator) an additional edit icon may/will be displayed alongside the print and the email icons if the issue is one they are ‘identified by’ as raising the issue OR in they are an issue administrator. (See front end edition screens.)

This screen is also shown if the links are enabled for the all issues display, where the appropriately selected issue is then displayed.

Figure 4.56. Single Issue Menu Required Settings

Single Issue Menu Required Settings

The above display illustrates the only required setting for a single Issue Menu display. The various display options are shown in the following figure.

Figure 4.57. Single Issue Menu Display Options

Single Issue Menu Display Options

Figure 4.58. Child Link Display Option

Child Link Display Option

The child link display options impact the display of any issues accessed from the link on the List Issues Display, if it is enabled.

If there are any associated Custom Fields associated with the specific project (or sub-project) to which this issue is defined as being connected with then there will be another panel displayed with the custom fields and their specified entries. This is discussed in more detail in the section Custom Fields later in this document.

[Note]Note

Take care if you decide to show the progress field to the general public. The reason is that if you use the default setting a guest user's email address will be inserted into the progress field and hence be visible to the general public. Release 1.2 introduced the idea of capturing the details in the it_people table as an alternative, in which case the user details are NOT stored in the progress field of the issue. If using release 1.6 one could simply choose to not publish this specific progress record.

Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries