We recently had to perform a shutdown of JIRA which we did in the documented manner however, on restarting Greenhopper has stopped working correctly. The primary problem seems to be that it doesn't seem to understand the resolution status of issues any more which results in the planning board thinking all resolved issues are actually just "In Progress" rather than "Done" and all resolved issues are completely missing from the Task board. Until we get this fixed, we are very reluctant to use JIRA/Greenhopper for fear of making the problem worse.
I think your problems comes from your TaskBoard mapping.
Simply go into your project > GreenHopper > configuration > TASKBOARD MAPPING and verify that you columns are properly mapped.
If not simply correct the mapping.
GreenHopper should now react better in the PlanningBoard and TaskBoard.
No worries on the data side, GH does not alterate any data.
It is just displaying whatever you have in JIRA. Here it seems that GH for some reasons (might be a problem in the sutdown) lost track of the mapping thus the computation of the progress bar is wrong.
This has worked - thanks. The problem now is that all of our individual projects need updating. We will do this but it would be good to try and understand why this configuration may not have saved during the last shutdown? Any thoughts? Also, do we have a good way of avoiding this next time? Should we take a backup of Greenhopper?
This is actually the first time I see this issue raised.
Did you guys performed any backup restore before shuting down JIRA?
The backups should not be needed.
Anyhow your JIRA should be backing up automatically if you do not have an automatic backup of your database in place so GH is being backuped.
Now the only other reason I see is the shutdown itself.
Something might have happend. A concurent update of the database while JIRA was shuting down.
We didn't perform any backups but did to a normal shutdown. It's a shame we can't be sure what happened so that we can avoid this in future although we're thinking of upgrading anyway which might help with this and a few other small issues we're having in Greenhopper.