Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4113

Risk Status - Exposure calculations appear to be broken.

    XMLWordPrintable

Details

    • 1
    • Severity 3 - Minor
    • No

    Description

      Issue Summary

      The Probability of Occurrence should be a value between 1% and 100%, but the available values are only 1 to 4. The same applies to the Level of Impact (which should be 1 to 10).
      The Probability of Occurrence has a wrong order as well.

      Steps to Reproduce

      1. Make sure there's a Risk in your current PI T1 config.
      2. Go to the Risk Status page
      3. Change the Extra Configs to Exposure
      4. Clicking on either of the Risks and changing their levels of impact or probability of occurrence only allows the user to select a value from Low -> Critical and the resulting numbers don't go above 4 in the exposure report.

      Expected Results

      Probability of Occurrence showing values between 1 and 100% (and not just between 1% and 4%)
      Level of Impact showing values between 1 and 10 (and not just 1 to 4)
      Need to double-check if the Total Exposure calculation is correct.

      Actual Results

      Calculations below. Even if the calculations are correct, the Probability of Occurrence has a wrong order.
      Probability of Occurrence: Low = 4%, Medium = 3%, High = 1%, Critical = 2%
      Level of Impact (1-10): Low = 4, Medium = 3, High = 2, Critical = 1
      Total Exposure: level of impact * Probability of occurence (converted from % to decimal)

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Issue Links

          Activity

            People

              9ca9aa5ad14e Sam Tsubota
              c1060921cc3a Enio Marques Junior (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync