Mass Updates and Audit Trails

Related Issues and Mass Updates

When a user performs a mass update and some of the records are part of relationship groups, no attempt is made to update the related issues to any single item. The reason for this is that there could well be thousands of issues in the mass update, and each one of them may in some way be related to other issues, causing ExtraView to ask the questions for each issue as to whether the related issues should be updated.

Related Issues and Audit Trails

You may add an embedded layout prepared to display related issues to a History Layout. As explained in the previous section about preparing layouts for Related Issues, these layout types always begin with the character string RELATED_. This produces a related issue display at the point in time on the history record when the issue was updated, not at the current time. When you configure this layout on the History Layout, remember that you may also need to set the relationship group name and the relationship group type.

There is a special field named RELATIONSHIP_GROUP_TXNS. This may be added to the History layout to see all the relationship group operations that occurred prior to and including the listed transaction time. Note that the audit trail for related issues cannot be displayed if ABBREVIATED_HISTORY is set to NO as the abbreviated history does not use any layout for its display.

Related Issues and Report Output Types

When a report contains a related issue display, it is treated as follows for the various report output types. The reason for this is that some output types are deliberately formatted to make it easy to use the data as input to other processes or programs. Having a variable number of items of data from the related issues within these reports will make these operations impossible.