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

[JIRAALIGN-1507] WSJF: Incorrect calculation where multiple PI's added to an Epic

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • Stubborn Dragons - BBSH
    • None

      Issue Summary

      Scenario: An Epic has 3 PIs identified on it. There has been a WSJF applied to two of the three PIs. FY 20.1 = 14 and FY 20.2 = 11.2. When viewing this epic without a PI selected in T1, it is adding together the WSJF values and displaying 25.2 in the WSJF column.

      Steps to Reproduce

      1. Create an Epic and assign multiple PIs
      2. Apply WSJF to one or more of the assigned PI's
      3. Review the combined WSJF value in the grid

      Expected Results

      Per PdM: summing all WSJF for epics does not make sense. Instead, we should not show PI-specific data if there's no PI selected. We should render a "" symbol in the column for each row, with a tooltip for each "" explaining "Select a PI(s) to render WSJF values."

      Actual Results

      WSJF values are summed

      Workaround

      There is currently no known workaround for this issue
       

        1. image-2020-12-07-16-35-50-706.png
          image-2020-12-07-16-35-50-706.png
          23 kB
        2. image-2020-12-07-16-36-47-205.png
          image-2020-12-07-16-36-47-205.png
          23 kB
        3. WSJF.png
          WSJF.png
          26 kB

          Form Name

            [JIRAALIGN-1507] [JIRAALIGN-1507] WSJF: Incorrect calculation where multiple PI's added to an Epic

            Caz (Inactive) added a comment -

            Closed in 10.87, shows an empty column and a warning icon by the WSJF column header on the grid if there's no PI selected

            Caz (Inactive) added a comment - Closed in 10.87, shows an empty column and a warning icon by the WSJF column header on the grid if there's no PI selected https://jira.atlassian.com/secure/AddComment!default.jspa?id=1548742

              cgottlieb@atlassian.com Caz (Inactive)
              cjeggo Chris Jeggo (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: