You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are a SAFe Agile environment and have over 15 teams/projects sources. I created a JQL Query across the Train to get all issues from all teams. I filtered down to only give me Epics and the result is 183 issues. I created a Portfolio Plan using the saved filter however the plan only shows 180 issues.
What is causing the mismatch?
Hi @Ray Gorbea
You raised a good question that has quite a few possible causes. I'll note all/most of them here. The Portfolio plan shows you a different amount of issues than your JQL filter because you may have:
If the above options do not resolve your case I would recommend you contact support here: https://support.atlassian.com/
Roi Fine | Product Manager
Thank you for the information...unfortunately after going through all the options listed none of them resolved the issue. It seems that the Portfolio plan is very picky about the status of the issues. When we looked at one Epic that was not in the plan, we noticed it had a status of Closed but had Stories that were still Open. We decided to Reopen the Epic. Once open it appeared on the Portfolio Plan. We then checked another missing Epic. It was also Closed, but had no Stories at all. We Reopened that Epic, it appeared on the Plan. There were other Epics showing on the Plan that were Closed, but their Stories were Closed.
We also noticed that by default the Plan doesn't show all issues over the time of the PI. We had to manually change the setting to view from the last quarter. There is still missing stories from the plan which we are investigating.
Is there a list of behavior attributes that should be followed to properly view all issues in the Plan? This should be more user friendly.