Epic Link is not updating

Question

I have given permission to Administrator and Scrum Master to edit an issue.

* Scrum Master add epic link, it shows success message but no epic link appears on issue screen.  
* Administrator add epic link, it shows success message and epic link appears on issue screen.

Why Scrum Master is unable to add epic link?

Where I am doing mistake?

What I am missing?

Michiel Schuijer_yj4jdb · Answer

I came across this issue today and can confirm it is the "Edit issue" permission in the project/Epic you are trying to add in "Epic link".

People don't always realize that not only do you need (Edit) permission in the project's issue where the epic link field is, but also the project where the Epic is.

Always be sure to check project permissions with the project administrators of each project!

p.s. the role "Scrum Master" is often granted the permission to "Manage Sprints" but this is not the same as "Edit Issues" and the role could not even be added to any permissions in the permission scheme, so it is worthwhile confirming the permissions in each project involved.

Petter Gonçalves · Answer

Hello @Tauqir Rao

Thank you for reaching out.

Please, try the following steps to troubleshoot why the Epic link is not being updated when your Scrum master tries to update it:

1 - Navigate to your project > Project Settings > Permissions > Use the Permission helper to double-check that your Scrum master is properly configured with the Edit Issue permission in both issues (Child and Epic). If both issues are in different projects, do the same steps in each project and provide us with a screenshot of your permission helper results.

2 - Ask your Scrum master to use a different browser or in incognito mode and try to link the issue again, checking in the Javascript console of the browser if any errors are returned. Also, provide us what is the browser version that your scrum master is using

3 - Take a look at the Atlassian.logs to see if any error is returned when the Scrum master tries to link the issue to the Epic.

4 - If possible, ask the Scrum master to try the same steps logged in the Administrator's desktop, checking if the same problem reproduces.

Let us know if you have any questions.