Workflow Transitioned without Mapping - Any resolution?

[Krista Nicol]

A teammate of mine transitioned the workflow for a project with thousands of issues and accidentally mapped everything to an "open" status. Is there any way that we can resolve this?

We can see what the status was before it transitioned, so we can manually go through and update these issues to their previous status but with the amount of issues there are in the project we are trying to determine if there is another solution. Any help is appreciated!

[Kathy Hart]

There is not a magic undo button, as you already realize, no doubt. 

Your quickest fix will probably be to write a query for each previous Status, meaning one query for all issues that were transitioned by "that teammate" on "date" where Status WAS "In Progress. And another similar one where Status WAS "On Hold", etc. 

Then for each query, you'll want to have a good look at the issues it returns to make sure they are what you are looking for. Then use Bulk Change to transition them back to "In Progress", or whatever Status that batch was in before. 

This may be a little tricky because WAS may not necessarily return the Last Status the issues were in, so review the returned tickets carefully. You may have to play with Date parameters relating to the Statuses. 

Here is the documentation for advanced JQL searching. https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-939938733.html