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

Only JIRA-ADMINISTRATOR group member can add EPIC LINK

Tauqir Rao

Hello Peers,

I have given EDIT permission to SCRUM MASTER Role. but SCRUM MASTER unable to add EPIC LINK successfully. Consider following scenario for better understanding

SCRUM MASTER
1. Scrum Master can edit the issue
2. While editing, when Scrum Master add EPIC Link, it shows pop-up "Issue is successfully updated", but no EPIC LINK added.

JIRA-ADMINISTRATOR

1. JIRA-ADMINISTRATOR can edit the issue
2. While editing, when JIRA-ADMINISTRATOR add EPIC Link, it shows pop-up "Issue is successfully updated", and EPIC LINK added successfully.

WHAT I WANT

SCRUM MASTER should be able to add EPIC LINK successfully, like JIRA-ADMINISTRATOR

What I am missing, what is workaround for it?

Thanks

Accepted answers

Soumya Shukla

Hi Tauqir,

As we figured out on the related Support Request you raised for this behavior, this was a cache issue and restarting the Jira server solved the issue for you.

Please 'Accept' this answer so that it helps other users who come across a similar issue in the future.

Best Regards,
Soumya Shukla | Atlassian Support

All comments

Monika Rani

@Tauqir Rao can you check the permission scheme again for the scrum master role. Is the scrum master has the correct permission to perform this task? and please check the screen scheme too.

Tauqir Rao

Yes, SCRUM MASTER has the required permission

Pete Singleton

Is the Epic you are linking to part of the same project as the issue you are linking? The user will need Edit permissions on both projects if not.

Tauqir Rao

It is the same project.

Pete Singleton

Do they also have the "Link Issues" permission?

Tauqir Rao

Yes, they have Link Issues permission

Soumya Shukla

Hi Tauqir,

As we figured out on the related Support Request you raised for this behavior, this was a cache issue and restarting the Jira server solved the issue for you.

Please 'Accept' this answer so that it helps other users who come across a similar issue in the future.

Best Regards,
Soumya Shukla | Atlassian Support

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server