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
I have many advanced roadmaps plans that work very well except for one. It is an ordinary project with a Kanban board. I have tried setting the Issue Sources to board, project and filter and none of them work. I am assuming there is something special about how this project is defined that is keeping it from working. Any suggestions on what might be happening?
@Thayne MunsonYou might check your "Exclusion Rules" to ensure that you have INCLUDED some releases. It's seems a little counter-intuitive that they are listed under the Exclusion Rules, but if your issues are tagged with a Release (FixVersion) and that Release isn't INCLUDED, then none of those issues will show up. The same place will also show you Releases that you have NOT selected so it really covers both.
I guess ultimately it depends how you look at the world and whether their new design makes sense. Do you perceive it as ADDING releases to a plan that has no releases, or do you perceive it as REMOVING releases to a plan that inherently includes all releases? That is the question.... Clearly the designers see the world as the latter view :)
Thanks Aaron. There are no releases for my project. But, I did discover that the workflow does not update the Resolution field when closing issues. Based on the documentation I found on Atlassian, Resolution is a critical field in Jira and could have an impact on my AR plan as well as other Jira gadgets.