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; } } }

How can I bulk change "epic link" to "is parent of" link?

Cornelius Dufft_he7ghx

- I have about 1.000 Epics and need to move them to issuetype "Feature", to comply with our business outline.

- The Epics have several Stories and/or Tasks linked per "Epic link" under it.

- When I try to move an Epic to issuetype Feature, the "Epic link" gets lost. I am loosing the link to the previously linked Stories and Tasks. But the "is Parent of" links (like all other link types) are retained as intended.

- I think if I could automatically (bulk change or admin change) change the "Epic link" of these Epics-Stories/Tasks to "is Parent of" links first, these links would be retained and I could safely move the issuetype Epic to Feature later because

How can I bulk change "epic link" to "is Parent of" link?

Accepted answers

Trudy P Claspill

Hello @Cornelius Dufft

Welcome to the community.

The Bulk Change feature is not able to do what you want. However, you could do this with an Automation Rule. Are you familiar with the Automation feature?

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Automation Rules are limited in how many issues they can process in a single execution, so you would likely have to do this in batches. Refer to this

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

There are also limitations on how many executions of Automation Rules you can have for free, so you might want to also review that before starting the process to ensure you are not going to go over your limit. Refer to this.

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

All comments

Trudy P Claspill

Hello @Cornelius Dufft

Welcome to the community.

The Bulk Change feature is not able to do what you want. However, you could do this with an Automation Rule. Are you familiar with the Automation feature?

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Automation Rules are limited in how many issues they can process in a single execution, so you would likely have to do this in batches. Refer to this

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

Bill Sheboy

Hi @Cornelius Dufft -- Welcome to the Atlassian Community!

Yes, and...to Trudy's answer:

This form of change can be quite disruptive, as you note for the change of issue type. This is one reason Jira as a special operation for this: Move. I encourage you to find a way to backup the information before starting, as that may help with any recovery you need to do.

Please consider working with your site admin to perform a site backup, or to export the epics and their child issues. The latter would provide you the data needed to later reconnect the children to the moved parents using issue-import if something goes poorly in the conversion.