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
Our greenhopper Scrum boards appear to have been corrupted. Specifically the Kuliza board had 25 Sprints of history, but now the plan tab only shows a few sprints and almost no issues in those sprints.
I had been experimenting with changing the status of the Done column to something other than closed in the 25th and 26th sprints. I don't know if its related but thought I would mention it.
As part of this issue I want to know if you can even have a jira status other than 'closed' mapped to the 'Done' column on Scrum boards to have the boards work correctly.
Please let me know ASAP.
Yes you can, GreenHopper will read the status mapped under the right most column to determine whether an issue is consider as Resolved (and do burndown).
For example, if you set status In-Progress under the right most column, all the issues with status In-Progress will be considered as Resolved thus will not appear in the Plan Mode and Work Mode. Is this the case here?
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.