JSM role permission seems to override permission scheme settings

RDaridan May 30, 2023

Hello everyone,

 

I had a strange behavior using "Create linked issue" :

when trying to create the new ticket message "You do not have permission to link issues in this project".

I added the group to the link issue permission and check that the group also has the "Create issue" etc. but user can't create link issue.

I had to add the group to the project role "Service desk team".

I was told myself that using groups in permission scheme override role permissions but it seems that it is false.

Is someone can confirm that using JSM groups added in permission scheme is not sufficient to give the same rights defined by project roles ?

Thanks in advance :)

Capture.PNGCapture2.PNG

2 answers

0 votes
Najjar _Innovura_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 30, 2023

To successfully link an issue, it is necessary to have the "Link issue" permission in both the source and destination projects. Based on the provided screenshot, it appears that you have the necessary permission in Project 1.

To ensure a smooth linking process, it is essential to verify that you also have the "Link issue" permission in the destination project. Without this permission, you may encounter issues when attempting to establish the link between issues from different projects.

To check and adjust the permissions in the destination project, please follow these steps:

  1. Navigate to the destination project in Jira.
  2. Click on "Project Settings" (located in the lower-left corner).
  3. Select "Permissions" from the sidebar menu.
  4. Locate the "Permission Helper" and ensure that your user account or the relevant user group has been granted this permission.

By ensuring that you have the "Link issue" permission in both the source and destination projects, you should be able to successfully establish the desired issue links.

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2023

Hi Daridan,

Check the Permission Scheme associated with the project to make sure you have the Link Issues permission. 

RDaridan May 30, 2023

Hello @John Funk ,

already done : the image I attached was just an example but I checked all permissions connected to the message. Link Issues wasn't ok and I corrected :)

RDaridan May 30, 2023

To complete, operations allready done :

  • add the group to "Create issue" permission
  • add the group to "Link issue" permission
  • add the group to "attachment permission"

Problem still here.

The add the group to projet role "service desk team" problem solved. Service desk team has the link issue permission.

 

The purpose was to allow creation of ticket in a process of escalation.
This only happen when creating tickets from a JSM project to another JSM project.
Creating tickets from a JSM project to a JIRA Software project is ok.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2023

Great to hear about the progress! So is everything okay now? 

RDaridan May 30, 2023

Not really, I think I badly expressed my purpose : 

In JSM, groups used in permission scheme are not priorised over groups used feeding a role in project role ?

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2023

No, there are no prioritization of the groups/roles/individuals attached to permissions. Just that they have the permission or they don't. So if someone is in a group but not a project role and the project role is not granted the permission but the group is, then the user still has that permission. 

RDaridan May 30, 2023

Thank you ! 

Could my problem be because we are using multiple JSM projects and trying to link issues from one JSM project to another JSM project?

Suggest an answer

Log in or Sign up to answer