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

[JIRAALIGN-1048] The "None Applicable" card doesn't filter Epics based on Tier 1 selection

    XMLWordPrintable

Details

    • 2
    • Severity 3 - Minor
    • Batman! - RHP8

    Description

      Issue Summary

      The card "None Applicable" in the Drill Down graph for Themes, are counting points from Epics that are not part of the same Portfolio or Program, not being filtered by the Tier 1 selected.

      Steps to Reproduce

      1. Go to PI (Release) Progress
      2. Select a Portfolio and PI (Release) in Tier 1 & 2
      3. Select "Are we going to finish the PI on time"?
      4. Select "Drill Down"
      5. Then View Themes (Business Initiatives)
      6. The "None Applicable" card considers Epics from other Portfolios or Programs

      Expected Results

      Only Epics associated with the Portfolio and/or Program selected in Tier 1 should be considered in the "None Applicable" card.

      Actual Results

      Epics associated with other Portfolio and/or Program different from the selected one in Tier 1 are being considered in the "None Applicable" card.

      Workaround

      N/A

      Attachments

        1. FilterDoesntWorkEpics.png
          FilterDoesntWorkEpics.png
          64 kB
        2. FilterDoesntWorkTeams.png
          FilterDoesntWorkTeams.png
          35 kB
        3. NoEpicNoThemeFeature.png
          NoEpicNoThemeFeature.png
          47 kB
        4. NoEpics.png
          NoEpics.png
          29 kB
        5. ReleaseProgress.png
          ReleaseProgress.png
          37 kB
        6. StoriesNotFromEpics.png
          StoriesNotFromEpics.png
          44 kB

        Issue Links

          Activity

            People

              kbyrd@atlassian.com Kyle Byrd (Inactive)
              amacedo@atlassian.com Alessandro Macedo
              Votes:
              3 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync