nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Fix required - Issue type story got updated to Story(Migrated) after a new project was imported

srikanth_rao

Issue:

The issue type "Story" is now showing as "Story (migrated)" in one of the projects.

This issue seems to have occurred after a project was imported.

Steps taken:

I found one solution here. However, since I am new to this, I am not sure how to proceed. I am looking for a possible solution on how to revert "Story (migrated)" to "Story" and in this process restore all the older tickets that have "Story (migrated)" to "Story."

Also, please help me with steps on how this can be avoided in the future.

Please let me know if any other details are required.

Any help is much appreciated!

Thank you!

Accepted answers

Thorsten Letschert _Decadis AG_

Hi @srikanth_rao ,

And a warm welcome to the Community!

To fix your issues, you might want to

Make sure your "correct" issue type "Story" is still available in all the relevant projects.
Run a search for the wrongly associated issues, e.g. type = "Story (migrated)"
Select "Bulk change" from the meatball menu in the upper right
Within the bulk operation dialogue
1. Select all of your issues in Step 1 "Choose Issues"
2. Select "Move Issues" in Step 2 "Choose Operation"
3. Select the correct issue type(s) in Step 3
4. Read through the details in Step 4 and confirm - you'll probably want to make sure not to send emails for this update

From the conversation within the ticket you've mentioned, I'd assume that this supposedly bug should not be there anymore. If that's not the case, you might want to reach out for the official support.

Greetings from Germany,
Thorsten

Lucas Knorr

Hi @srikanth_rao

You are right about the cause of your problem. Objects that have been migrated from another instance/site often create duplicates if the object already exists in the target instance.

What I would do in your case is to write an automation rule, which updates the issue type from the migrated one to the original one.
You can use a scheduled trigger with the JQL "issuetype = story (migrated)" together with an edit issue action to change the issue type.

Before you actually change the issue type, you should check the issue type screen schemes, issue type schemes and all other configurations aswell. The goal is to replace the migrated issue type in every configuration possible and delete the migrated issue type after that, so that there only leaves

From my experience, Atlassian Support does not offer any meaningful support on this topic. But it certainly doesn't hurt to open a ticket.

All comments

Thorsten Letschert _Decadis AG_

Hi @srikanth_rao ,

And a warm welcome to the Community!

To fix your issues, you might want to

Make sure your "correct" issue type "Story" is still available in all the relevant projects.
Run a search for the wrongly associated issues, e.g. type = "Story (migrated)"
Select "Bulk change" from the meatball menu in the upper right
Within the bulk operation dialogue
1. Select all of your issues in Step 1 "Choose Issues"
2. Select "Move Issues" in Step 2 "Choose Operation"
3. Select the correct issue type(s) in Step 3
4. Read through the details in Step 4 and confirm - you'll probably want to make sure not to send emails for this update

Greetings from Germany,
Thorsten

Thorsten Letschert _Decadis AG_

Addition:

While I was checking the easiest way to remove the wrong issue type, "Story (migrated)", I saw that the "Delete Issue Type" now comes with a "Migrate Issues" button. That being said, the first and second steps mentioned above might be replaced by heading over to your issue type settings (%yourSite%.atlassian.net/jira/settings/issues/issue-types) and selecting the "Delete" option for "Story (migrated)." The next dialogue should show the number of affected issues and the "Migrate Issues" button.

Lucas Knorr

Hi @srikanth_rao

You are right about the cause of your problem. Objects that have been migrated from another instance/site often create duplicates if the object already exists in the target instance.

srikanth_rao

Thank you so much for the quick response! I was able to use the steps mentioned earlier and resolve the issue, I will take a look at the addition mentioned and keep a note of it.

srikanth_rao

Thank you so much for the suggestion! I was able to go and fix this issue with all the projects.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud