-
Bug
-
Resolution: Fixed
-
Low
-
10.110.3, 10.130.2
-
2
-
Severity 3 - Minor
-
No
Issue Summary
This is reproducible on Data Center: (yes)
The Strategic Driver Report shows all Business Epics assigned to a Theme regarding what is selected in the PI dropdown
Steps to Reproduce
1. Create a Business Epic and assign 1 or more PIs
2. Create a Business Initiative (Theme) to associate that Business Epic with, assign to PIs that include and exceed those associated with that Business Epic
3. Using the Search box, type in Strategic Driver
4. Select the Strategic Driver Report option
5. Using the Portfolio drop-down, select your Portfolio
6. Using the Program drop-down, select your Program
7. Ensure you Do not set PIs from the Configuration Bar so you can select PIs from a drop-down list on the report
8. Select each available PI from the Strategic Driver Report PIs drop-down list
9. Observe that our Business Epic appears on the report for every PI, including those that exceed the range of the PIs associated with the parent Business Initiative (Theme)
Expected Results
The report should display the Business Epic that is only associated with the selected PI
Actual Results
The report displays the Business Epic for all PIs in scope for the parent Business Initiative (Theme) and those that are not associated with the Business Initiative (Theme) regarding the drop-down filter selected PI
As per the screenshot below, the PI selected was 11, however, Epics from PIs CPP are shown in the list
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- is duplicated by
-
JIRAALIGN-6335 Strategic Driver Report - Add filter ability to Epic list
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
- resolves
-
-
[JIRAALIGN-4297] PI Drop Down Filter is being ignored on Strategic Driver Report
Hi, if the resolution of this bug is set to "Won't Fix", then would you be willing to clear out the Fix Version field to remove any association between this bug any JA version?
Hi everyone,
Thank you for sharing your feedback.
Over the past several months, Jira Align Product and Engineering teams have reviewed over 1,000 JAC tickets in an effort to better understand the biggest problem areas, and make a concentrated effort to respond to your feedback more efficiently.
With this renewed focus and organization, we have decided to deprioritize and close this ticket. Here are a few reasons this ticket might be getting closed:
- The ticket had an impact score of <4 (combination of watchers, participants, votes and linked issues)
- The bug was older than 18 months (from Oct 1, 2022) with an impact score of <=6
- The bug was created more than 30 months ago
- The bug was part of a component (functional area) listed for deprecation
Moving forward, you will notice the following:
- all existing tickets with a bug status will be addressed within the next few quarters;
- all new tickets with a bug status will be addressed according to Atlassian's Cloud Bug Fix Policy;
- all new and existing tickets with a suggestion status will be considered as part of our product roadmap, which will be communicated during our quarterly roadmap webinar;
- all tickets with a won't fix status will be deprioritized.
To elaborate on tickets with a suggestion status, we will either create new projects that address the underlying issue, or incorporate these tickets into existing projects.
Thanks, Sam Ugulava | Sr. Product Manager
Hi everyone,
We've fixed this bug in the upcoming release of an updated strategic driver allocation report that will be available in release 11.6. For more information about the updates we're making to the report, please check out the announcement in the Atlassian Community.
Best regards,
Sam Tsubota
Senior Product Manager