Quicklist layouts and only Detailed Report layouts can be defined for each Business Area in your system. These reports are defined within the layout editor, in exactly the same way that screen layouts are created and maintained. The Quicklist and Detailed Report that are created at run time are dependent upon the current Business Area and Project of the user. The following security permission key is useful to understand when creating and maintaining the Quicklist and Detailed Report.
|
PR_RESOLUTION.QUICKLIST |
Controls access by user role to the Quicklist report. Most user roles should be given this privilege. |
There are several points that you should be aware of when creating report layouts:
-
There is a field in the layout list named VIEW_BUTTON. This allows you to place the drill down button to the detailed report on the screen. Most often used on the Quicklist, and never used on the detailed report itself.
-
There is a field in the layout list named HISTORY_BUTTON. This allows you to place the drill down button to the history report on the screen. The user must have read permission for the PR_RESOLUTION.MENU_HISTORY security key in order to see the button on the screen.
-
There is a field in the layout list named EDIT_BUTTON. This allows you to place the drill down button to the edit issue screen.
-
There is a field in the layout list named DELETE_BUTTON. This allows you to place the delete issue function on a report. The user must also have privileges to the PR_RESOLUTION.DELETE_BUTTON security key in order to be able to delete issues.
-
You may want to use the Highlight layout element attribute to alter the display color of some fields. For example, you may make critical issues appear in red. If you do this, then the color used is defined in the behavior setting named HIGHLIGHT_COLOR.
-
If you have a dependency within one field of a layout with another field on the layout, such as Highlight, then both fields must be on the layout.
