Jira Epic Converted to "User Story". Need Rollback help.

[Laxman Prasad Kuppili]

Team,

We have certain Jira types like Epic, New Feature, User Story, Task, Tech Story, Spike Story for our project.

Epic contains the list of User Stories. Every Single User Story contains list of bugs and tasks associated with them.

So, we have accidentally converted an Epic to User Story. So, all the User Stories which were tagged to epic before converting to a User Story have lost the linkage.

So, it is difficult for us to identify the list of User Stories that were originally tagged to an epic (before converting to User story). 

How can we rollback this conversion or how to track the list of Jira stories that lost the Epic link linkage?

[Walter Buggenhout · Accepted solution]

Hi @Laxman ,

I don't really have a test environment where I could quickly reproduce the case you describe - and not eager to try it in full, to be perfectly honest 🤗

I expect that your stories were previously linked via the parent field to the epic before. I assume that the issues were all updated at the time of your conversion and I would also expect the parent field on those issues is now cleared.

If you can approximately remember when you did the change, the following filter should help you get close to the impacted User Stories:

Issuetype = "User Story" AND Parent IS EMPTY AND Updated > startOfDay()
AND updated <= Now()

The last part is my assumption that you did this change today; but obviously, that's where you can refine. The last part is not really necessary as you can't update issues in the future; just added that part to indicate that you can also narrow done the timeframe between start and end dates.

Hopefully you get a short list. You should then be able to check the issue history of those user stories (on the issues themselves) and see if the parent field was cleared.

You'll need to move the User Story back to an Epic and then, once you've identified the linked User Stories, link those back to the Epic. There is no undo option for mishaps like this, so you'll have to do some detective work here, unfortunately 🔍

Hope this helps!

[Laxman Prasad Kuppili]

This approach worked @Walter Buggenhout 

Thank you!