| Field Name | Title | Definition |
| ATTACHMENT | Attachments | This field provides visibility of attachment history within the history of an issue. There is an accompanying permission key named PR_RESOLUTION.ATTACHMENT_HISTORY. This field provides a display of a record of which attachments were added or deleted when the update to the issue was made. However, if you are using the behavior setting named ABBREVIATED_HISTORY, then the attachment history is still shown, as part of each history entry |
| HIST_RANGE_END | Historic data filter | This field is used as a report filter to show the results as of a specific point in time. If this is selected, the results returned by a query are not the results as of the current time. This allows the user to go back in time and determine what issues looked like as of the date/time entered. This is also used within the evhist CLI command to determine the end date of transactions being generated |
| HIST_RANGE_START | Historic data filter (start) | This field is used within the evhist CLI command to determine the start date of transactions being generated. |
| MINI_HISTORY | History |
This is a UDF with a Custom display type that can be placed on layouts (typically edit screen layouts and detailed reports. This field generates an area that is about the width of your screen, that displays, by default, the status change dates and the person responsible for the change. If you are creating this field in your own environment, then make certain that you set Allow selection on reports to Yes in the data dictionary, and that you provide read access to the field for the roles that are allowed to see the information.
There is a behavior setting named MINI_HISTORY_FIELDS that is used to define the names of the fields that are displayed within the mini-history area. By default, these fields are STATUS, TIMESTAMP and ASSIGNED_TO. The first field is usually the STATUS field, and it is changes in the values of this field that trigger a new box being displayed. You may use any User Defined Field for this first value, as opposed to using the inbuild STATUS field. Beyond the first value in the list, the only valid fields that can be displayed are: SEVERITY_LEVEL, PRIORITY, STATUS, PRODUCT_NAME, OWNER, TIMESTAMP, ASSIGNED_TO, PRIVACY, LAST_CHANGE_USER, ALT_ID, AREA, PROJECT, CATEGORY, RESOLUTION, PRODUCT_LINE, DATE_LAST_STATUS_CHANGE, CONTACT, ORIGINATOR, and HIST_TIMESTAMP. In total, up to five fields can be displayed. You may alter the width and height of the field by setting a width and height (both measured in pixels) into the default value of the field in the data dictionary. Use a delimiter of a semi-colon between the values. For example, a default value of 1000;100 will set the size of the field to 1,000 pixels wide and 100 pixels high. Note that you must be precise with the syntax of the default value as no error checking is performed. If you do not provide a default value, a width of 900 pixels and a height of 80 pixels will be assumed. If the field is placed on a detailed report, then the standard width of the detailed report is used, and the height of the field will automatically expand as required, so that no scrolling takes place. This allows the user to print the detailed report and see all the data. An example is: |
 The MINI_HISTORY field |
||
| NOTIFICATION_HISTORY | Notification History | This field is placed on History layouts to provide a record of the users who were sent notification at each update of the issue. There is an accompanying permission key named PR_RESOLUTION.NOTIFICATION_HISTORY. This field provides a display of a record of the users who were sent a notification upon the update to the issue. However, if you are using the behavior setting named ABBREVIATED_HISTORY, then the record of email norifications are still shown, as part of each history entry |
| PRODUCT_NAME_HIST | Historical Product Reference | This field refers to the name of a product (PRODUCT_NAME) within an issue’s historic audit trail |
| RELEASE_FOUND_HIST | Historical Release Reference | History is maintained on repeating records within ExtraView. This field refers to that history |
| RELATIONSHIP_GROUP_TXNS | This field provides visibility of related issue transactions within the history of an issue. There is an accompanying permission key named PR_RESOLUTION.RELATIONSHIP_GROUP_TXNS. This field provides a display of a record of changes to related issues to the current issue. However, if you are using the behavior setting named ABBREVIATED_HISTORY, then the related issue transactions are still shown, as part of each history entry | |
| STATUS_HIST | Historical Status | Full history is maintained on all status changes to issues. This field refers to the status history |
