You can also bulk modify issues that are unresolved by transitioning them to "In Review" and bulk updating them again back to "Done" which then correctly set the resolution field. Unfortunately this technique means that all your issues are now resolved on the same day so your graphs etc show a big spike on one day.
For some reason this bug occurs after a few days with any of the default workflows in Jira, but it's not too big a deal if you spot it early and fix the workflow to resolve issues correctly.
As for the Jira/Godzilla thing, I always thought it was a reference to Mozillas Bugzilla, which I thought was kinda cool :)
Hope that helps!
Bastardized? It's the ACTUAL pronunciation, they just removed the "go" part.
It's nothing like making fun of the Japanese. I think trying to find racism where it doesn't exist has gone too far.
* Create a copy of your workflow * Add the outgoing transitions that you want to add * Change the workflow scheme to point at the new workflow
It's not super elegant but if you need to work around it you can.
Feel free to connect with me on twitter (@jsinkers).
That is extremely reaching, like on a hole new level. Do you get this offended in real life too if a coworker makes a joke? Genuinely wondering.
You can then bulk transition all your existing issues and the resolution will get populated correctly.
On the other side, my team has been bit by a bug from 2008 which prevents us from changing any ticket's state to Resolved. We can Resolve tickets, but their Resolution remains Unresolved. Since the Resolved state is central to most of Jira's built-in features, this means Jira has been broken for me since we installed it 6 months ago. The Your Issues default display shows all my tickets, including my closed tickets. The interface is not customizable enough to build workarounds for this problem.
Also, the name (bastardizing the Japanese pronunciation of Godzilla) always feels somewhat racist to me.