Epic Link & Parent Link movement to Parent

[Magdalena Zhisheva]

Hi all, 

How did you get prepared for the Epic Link & Parent link removal and replacing them with Parent field?

I went through all documents but still do not get it, for example: https://support.atlassian.com/jira-software-cloud/docs/maintain-epic-link-data-for-issues-above-the-epic-level/ here, there is a script 

issuetype in (<LIST OF ISSUE TYPES>) and "Epic Link" is not EMPTY and I assume that we need to perform some changes in the issue types above our epics, i.e. in our case initiatives. 

But still I do not get what should be done. In the same page there is the following: 

Maintain epic relationships

There are two approaches you can take to maintain the epic relationships on affected issues:

• If your issue hierarchy is important in its current form, you can add the epic as a linked issue (e.g. relates to).

OR

• If your epic link data is important to maintain, you can move any affected issue types to the base level in your issue hierarchy.
  
  If we add the epics as a linked issue to the Initiatives we will use the hierarchy between them in Advanced Roadmap and we do not won't to have this case. Currently, we are using parent link for having the linking between Initiatives and Epics.
  P.S. Parent field can't be added to the project screens.
  
  So, the question here is how did you prepared yourself for these changes?
  Any directions will be useful!
  
  Thank you all in advance! 

[Shubh Dasgupta · Accepted solution]

Finally got it working. Answer by Sharoon helped : https://community.atlassian.com/t5/Jira-questions/JIRA-Rest-API-authentication-always-returns-401-unauthorized/qaq-p/187181

The username IS the full email.

The password is NOT your password to login, but an API token. To generate an API token, go to https://id.atlassian.com/manage/api-tokens# and create a new one.