I got a question about using the migration of workflows using administration permissions for all of projects into the jira.
I done the migration from an old scheme to completely new one in order to make some changes on old one. After that when I apply updated old scheme with confirmation of "temporary statuses" to statuses from "updated scheme" I got unexpected troubles.
The problem is the following
All issues with "Done" resolution were changed to "Open" and finally 're mixed with logically correct ones. Based on information that initial count of issues is over 1000+ I need to make a complex approach (not a manual one) to revert it. Any ideas ?
This is two separate things. You talk about changing your workflows first, which is fine. But then you describe a problem which has nothing to do with the workflows. Workflows define the possible status for issues. Resolution is separate from that. Changing the workflow for issues will have no effect on the resolution. Using the workflows after the change could affect resolution as the workflows can set it as issues move through them, but the workflow change itself will not.
People mix up status and resolution a lot though, and often have shared names (done or fixed are both good words for both of them), so, first, we need to establish that the problem is status or resolution. Could you confirm which one is wrong?
Could you use a advanced JQL search to find the issues where status was changed by you during the time window where you updated the status?
The JQL would be something like this (you'll need to tweak the times):
status changed from "Done" to "Open" by currentUser() during ("2016/11/18 00:00", "2016/11/18 12:00")
Then use bulk transition (see "Transition multiple issues" section) to move them back to "Done".
Once you've got a search showing the list of issues you accidentally changed, use bulk change to transition through your workflow to get them back to "Done" status.
The option is here:
After clicking this, you'll go to a "Choose issues" screen, allowing you to further refine which issues you want to work on. I'd suggest testing this on one or two issues first.
Then it is steps 3 to 7 in the "Transition multiple issues" section from: https://confluence.atlassian.com/jirasoftwareserver072/editing-multiple-issues-at-the-same-time-829057529.html
How to transition multiple issues
- Perform a search with the required filters to produce a list of issues.
- Select Tools > Bulk Change.
- Select the issues you'd like to perform the bulk operation on, and select Next.
- Select Transition Issues, and select Next.
- Select the available workflow action. The actions available are dependent on the issues (and their associated workflows) that you have selected. Select Next.
- Select a value for any required fields for this transition, and if available, decide whether you'd like to send email notifications. Select Next.
- Review your bulk operation, and select Confirm when you are happy with the operation.
I don't know your workflow, so I can't tell you exactly which transitions you'll need to do.
As I said, test it on a single issue first to get the hang of it and make sure it solves your problem without unexpected suprises (e.g. make sure you don't send email notifications, you probably don't want to trigger thousands of those!).
And if you go to <your-jira-url>/secure/ViewProfile.jspa, does your activity stream show any changes made by you?
Does the workflow transition you are trying to execute have any validators on it that could be stopping it from working for the issues in question?
A test would be to do the following:
When you do this, does your workflow require completion of any fields / comments, etc to get it to "Done"?
If you can do it on a manually on single issue, then you should be able to do it in bulk on more than one.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs