I seem to have a workflow bug that is setting the resolved status to my default status "complete". This is even occurring on brand new issues creation, so I am a bit vexed!
I'm sure I can figure out my workflow bug but the bigger issue right now is "unresolving" all these issues that have been erroneously marked with a resolution status. My developers are unable to see the issues in their list because they are considered resolved.
Please provide a resolution right away.... this is a HUGE problem during a critical project and is making me and JIRA look very bad.
The default workflow wouldn't do this so sounds like you have made modifications? Is that right?
In any case you'll probably have to modify the workflow transitions to have it clear the resolution field when transitioning to an appropraite status. Maybe do this on 'start progress' transition or something.
I'd suggest in future try do these on a test install etc..
Colin is right. Any issue that has a resolution field set is considered resolved. You should make sure that the resolution field is hidden in all transition views except the one leading to complete/closed or any other status you use that indicates this. You also need to modify the workflow transitions to clear the resolution field when leaving the status.
A quick way out of your mess is to do this out of work hours...
If the jira.issue.editable property is set to false in the earlier workflow, then Edit may not be enabled. In that case, you can add a new transistion for your workflow from your current state and clear this property as well as clear the Resolution with post conditions.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot