I have another (newbie) question. We use JIRA as a database for books we are producing. The workflow part is very useful for moving lots of titles between editors, coordinators and graphic designers.
When we first started using JIRA, we transitioned some issues to our final state, where they are now locked and their status has been set to resolved. This is a small problem though, for numerous reasons, but the primary being that we can't edit the titles if something changes. We realised (too late) that we shouldn't transition any titles to the final state, which is a fine workaround for the titles we are producing now, but I am still left with 200 titles that I can't transition back in the workflow.
I have a feeling that I have to give someone(preferably the admin, myself) the permission to move "closed" or "resolved" issues back in the workflow.
Does anyone know a solution for this?
Our workflow("Production closed" is the one we want to avoid or move back from):
Thanks for helping out,
you have only to copy your current workflow, add a temporary transition from Production closed to any status you want, map this new workflow into your workflow scheme used by your project and confirm this operation. After that you are able to bulk transitioning the 200 "wrong" issues. If you like you can delete the temporary transition afterwards.
Now all the titles have been moved away from "Production closed" - so far so good. Their Resolution is still Done though. Is there a simple way to make them Unresolved, like the rest of issues? We dont really bother with the Resolution field, so it will make it easier if everything is just the same.
sure! There are several add-ons like with that you can do this. The way that I would prefer in your situation would be to add a transition from the new status to itself in the current workflow and add a post function to this. Choose the "set field value" post function and configure it to set the resolution to unresolve. After publishing you can bulk transition the issues you want to unresolve. Sorry, I think I hadn't read this in your first question. Otherwise you could have add the postfuntion the the first configured transition ....
Hope this helps!
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events