Deprecation of Epic & Parent Links

[Sue Wilson]

This morning we began to receive the following error message.  Some research seems to indicate this impacts Rest API (which I haven't been able to confirm use of since I did not build out this JIRA instance) and the changelog will be updated to IssueParentAssociation vs Epic Link or Parent Link.  What I cannot tell is whether or not I, as the JIRA Cloud Admin, need to make any updates.  We use and rely heavily on Epic Links, Parent Links, and Advanced Roadmap, so I want to be sure we are set up correctly to avoid any loss of data or use come 11/11/22.  Any insight would be GREATLY appreciated!!!

[Mikael Sandberg · Accepted solution]

You should have received an email regarding these changes and that email also included this guide to help you determine which issues that may be affected by the change and steps to maintain this data.

[Sue Wilson]

@Mikael Sandberg THANK YOU SO MUCH!!!  The link you provided answered all the questions I had. I did not receive an email with this information, but that could be because I have only been administering Cloud since February and was not immediately set up to receive such helpful information until months after the previous admin departed.  I truly appreciate your help!

[Carl Dichter]

The documentation does not tell us if parent properly replaces Epic Link when the issues are in different projects.

Will I be able to set Parent to an Epic in another project?

We must have bugs/tasks/stories which have no parent other than an Epic that is in a different project. This is because for every major feature, there is often an associated epic in an API or DevOps project.

[Mikael Sandberg]

@Carl Dichter This change will not affect the ability to link to a parent in a different project, every thing should stay the same as it is right now.

[Carl Dichter]

Are you sure that you can create a child in one project, and later change the parent link to an epic in another project?

We can't try that since we don't have the new field.

[Mikael Sandberg]

Yes, it will behave similar to how Parent is currently working if you are on Premium and have a hierarchy above epics. It is not limited to a single project, parent and children can be in different projects.

[Aaron Geister _Trundl_]

Is Atlassian making the change for us. Will they replace the current epic link and parent link for the parent field. 
Or 
Is this something that Admins will have to do? As of now I can make no change because we only have option for Parent Link and Epic Link available. 

We got the notification yesterday and it had panic among my Org. I am trying to validate anything I need to do to be ready for this on my side along with updating scripts with the new API and screen with the new field. 

Can someone validate what I will need to do. I read through the documents but it wasn't clear to me that I would or wouldn't have to make specific changes to our screens. Only that we would have to update API's. 

[Mikael Sandberg]

The switchover will happen automatically, you just have to follow the guide above to make sure you do not have issues that are not following the default hierarchy, if you do and do not take action those relations will not be preserved. The switchover will be based on the hierarchy that you have defined in your instance.