Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Greenhopper Scrum Boards Have Lost All History

Rob Bastian
Rob Bastian Jan 10, 2013

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.

Answer
Watch
Like Be the first to like this
599 views

2 answers

Suggest an answer

Log in or Sign up to answer
0 votes
vkharisma
vkharisma
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 11, 2013

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?

View More Comments
Reply
Rob Bastian
Rob Bastian Jan 17, 2013

What I've noticed is that the right most column will remove from plan and work mode, but the burndown charts are not updated correctly.

Like
0 votes
Timothy
Timothy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
Jan 11, 2013

Have you tried to re-index your JIRA?

Reply

Recommended Learning For You

Level up your skills with Atlassian learning

Jira Align Program Essentials

jira-align

Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).

3h Beginner
On Demand

Managing Agile Boards and Reports

Jira Software

Learn how to pick the right board type for your team and customize it to fit your specific requirements.

1.8h Advanced
Free

Atlassian Certified Associate

Jira Software Board Configuration

Jira Software

Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.

1h Intermediate
Certification
groups-icon
Agile
TAGS
AUG Leaders

Atlassian Community Events

See all events