View issue history

You can view triage and detection history for issues in your projects and tests.

There's more than one place where you can find issue history in Polaris. The Issues tab (Portfolio, select an application, select a project, and open the Issues tab) is used in this example, but you can view issue history wherever the issues table appears.

Note: Triage history is not branch-specific. All of the triage events for an issue (across branches in the same project) are shown.
  1. Select an issue with the checkbox on the left side of the table.
    Note: Issue history does not appear when you select multiple issues.
  2. Click Triage Selected or (if you only have observer access to the application) View Issue History.
    The Issue History panel appears withTriage information displayed.


    The triage timeline displays up to four of an issue's most recent triage events. A triage event can be either a change to an issue's triage status or a triage comment added to an issue. Select Show More + (near the bottom of the panel) to load up to 100 more triage events.

    Note:

    Triage events imported from third-parties. Triage events imported from third-party tools (by running external analysis tests) appear in the timeline with the text Imported from followed by the tool name; for example, Imported from Black Duck SCA indicates the event was imported from the Black Duck® SCA tool.

    Imported triage events are attributed to external users if the third-party tool provides this information. An external username is followed by the text (Imported). Imported by System indicates that the triage event could not be attributed to an external user. For more information about this feature, see Import results from third-party tools (limited availability).

  3. To view the issue's detection history, select Detection.


    Earlier detection events appear near the top of the list. There are three types of detection events:

    • First detected: The first test of the branch in which the issue was detected.
    • Absent: A test in which an issue is no longer detected.
    • Re-detected: A test in which an absent issue is detected again.
    Note: Detection history is branch-specific. Detection events for the same issue can vary between branches.
    Note: Detection events are only added to the list when an issue's detections status changes. For example, if an issue is absent in three consecutive tests, only one absent event appears in the issue's detection history—with completed date and time of the earliest test.