Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

migrate a custom issue link to parent-link

aya nayman
Contributor
June 19, 2022

Hello

 

We are migrating from server to cloud and we are using a custom issue link in Jira to create additional issue hierarchy "capability-epic"

We are using also additional issue type called "capability"

 

Now we are migrating to the cloud and we would like to also start using the parent-link that is built-in advanced roadmap

The question is how can we preform a migration of the existing epics and capabilities, after we move them to the cloud , to use the new parent-link instead of the custom "capability-epic" link. after the migration we would like to delete the custom link type and starting that point to use the parent link only.

 

Maybe there is a way to do it with automation or with a script ?

Please advise.

Thanks, Aya

1 answer

1 accepted

0 votes
Answer accepted
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 24, 2022

Hello @aya nayman ,

Thanks for reaching out, and the limitations on the migration assistant are covered in:

Noting:

What isn’t migrated

  • Classic plans

  • Plans that have issue sources as private filters

  • Unsaved scenario data

  • Saved views

  • User defined custom fields of type

    • Parent Link

    • Team

    • Target start

    • Target end

 

So as a post-migration step you could populate the issue link data using a CSV import to update the existing issues as covered in:

And if you need some additional help planning and running the migration please contact support and create a "Migration Support" request so we can help tailor this a bit more for your exact needs.

Regards,
Earl

aya nayman
Contributor
July 7, 2022

Hi ,

thanks fot your reply 

I tried like you explained to import CSV and it works.

so it was a simple CSV with 

epic key , epic summary , capability key.

 

the problem is how to export from jira server the csv and to get  the capability issue key , because when exporting from JIRA the "linked issues" field can show additional linked issues

 

so for this I used the add-on eazybi , I created an "Issue Link" dimension& measure for the capability-link. and

created a report to show epics and linked capabilty

 

another solution is to use the addon Xporter havn't try but I guess it can work as well

  

Like Earl McCutcheon likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events