Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can't create linked issue between Service Desk projects but have permission

My SD agents are receiving "You do not have permission to link issues in this project" when trying to create a linked issue in another SD project.  All agents have the Create Issue and Link Issue permissions in all SD projects through custom groups.  The agents can perform other functions such as Move between projects.

JIRA 7.6 \ SD 3.9


I'm having this same issue.  We're on JIRA 7.7 and JSD 3.10.  I've given the group the agents are a member of to Create issue, Link Issue, and Edit Issue and they still cannot create linked issues in the other SD projects.  All SD projects share the same permission scheme as well.

It looks like the JIRA Service Desk module is overriding my custom permissions setting I used to allow another group access to "Link issues".  Despite the users all having a JIRA Service Desk license, the agents that are not "Service Desk Agents" in the linking project is causing the error.

When we evaluated Service Desk we managed to get it working but now that we have implemented it, despite the custom role having all the necessary permissions, we cannot create the linked issues unless you are a Service Desk Agent or more. Any resolution yet?  Who at Atlassian can assist?

Is that what causes this? It's been bothering me for months, and all I could find previously was a post from 2013 about an older bug. 

Any solution would be great. 

We had to add the agents to the Service Desk Team role in both projects to get this working which is def not ideal.  Now we run into the issue of agents being assigned issues in the wrong project.  We're still on JIRA 7.6 \ JSD 3.9 and I don't think this has been resolved in the latest versions but I could be wrong.

Like Heather R likes this

We're on JIRA 7.9 \ JSD 3.12 it's still a problem for us. 

Hi all,

This is the related Atlassian ticket:

We had the same issue. Granting agent permission in destination SD project, users are able to create linked issues.

I created a group that just has browse permissions on the secondary work order sites. They are able to see the backend and view all the work orders, so its not ideal, but it does solve the problem of creating the links and getting them to appear. They have to transition to the front end though to make any edits.

Another thing that is important, is that you have to get it so that the workflow "runas user" is an administrator. I use a user i made when i first started using jira: 'SYSTEM', to do things like this.


but i create the links using workflow transitions, not by clicking a link button, so this may not work for you.



I am facing the same issue! My agents are not able to create a linked issue to another service desk, despite being given a developer role in it and the developer role given permission to create links. This isn't right!


They can create a new issue over there, which only saves successfully if the link itself is deleted before saving. 

Anyone tried to remove all permissions from the ServiceDeskAgent role (maybe not link issue) assign user with this role and assign the same user or group to another role which controls the permissions ?

Got the same Issue here and hope i don't have to recreate all permissions.

I have same issue, no update from Atlassian side?


Log in or Sign up to comment