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
In Jira plans, I am filtering to show only active and/or future sprints.
Tickets that were part of older sprints as well, do not show up in the plan.
Is this an actual bug, or am I missing something?
Not sure I follow your question... You're filtering to only see active or future sprints, but also expecting to see older sprints?? Seems like there is a conflict in your filter and expectations :)
That said, if you're looking to see PAST issues, make sure your history exclusion days setting isn't too small for what you're trying to capture. This is located on the configuration settings under the Exclusion Rules. Picture attached:
Hi Aaron, seems like you misunderstood my question. I will try to clarify.
I am ONLY interested to see tickets that are part of a current sprint or future sprint.
Tickets that were assigned to an older already completed sprint, but were moved to the next sprint as they were not completed, do not show up in the plan.
It seems that the filter does not work as intended.
If a ticket is part of an active sprint, it should be visible, regardless if it was once part of an already completed sprint.
Does this help?
Ah, yes, I misunderstood, apologies. I think it probably depends on the specific JQL driving your filter. I have been successful using the Filter input source, but it is obviously highly dependent on your source JQL filter. When you run your filter from the advanced Issue Search do your results contain the issues that aren't showing up on your plan?
Note: The Release/FixVersion field is also key to ensuring your issues are being displayed. This caused me much frustration at first, so it may be something to look into.