Show linked issues from other projects

[JiraYo]

Hey i am facing a probable permissions issue and i am just wondering a way around it. As it seems, linking issues does not seem to work the way i want it. here is the scenario:

ProjectA has an issue created. As part of that issues workflow, i have created a workflow transition that when clicked, generates issues in other projects on the site (projectB).

So a tech goes to create an issue on projectA, and populates one of my trigger fields. The workflow runs, checks the field, and creates an issue in projectB with the content of the field as the summary.

This all works fine, however when i go back to the issue in projectA, as a service desk rep on the issue, i cannot see the links for those other issues in the projectB site.

As a system administrator I can see the links fine, and they are created by the workflow in the SYSTEM user (another system administrator).

So i think this is a permissions issue, possibly with the browse project permissions. But i would hate to give my users on one project browse permissions on the entire other project. The user who creates the issue is also named either as a 'reporter' or "request participant" on the newly created issue in projectB, so shouldn't they have visibility of links anyway? if they browse to the issue manually, it is created and they can view it. Just the link does not appear for them, which is the nicest point of this system i am designing.

bug, or as designed?

[Alexey Matveev]

Hello,

Grant the Reporter to the Browse Projects permission in the project, where the linked issue is created. As you said the reporter in the linked issue is the reporter of the main issue.

[JiraYo]

yes but that could be anyone in the company. this opens up the backends to everyone? not something i want to do. people make internal comments, is one reason. and you could see literally every other work order.

it would be nice if jira, noticing that you dont have permissions on the backend, transparently makes the links go to a front end link (that they do have permissions to view). The problem is that linked issues just go to the backend view and not the front end customer view.

if i browse the front end customer view, the technician should be able to see it based on the organization being added to the issue however they cannot. hmm that should for sure be working... maybe something else is going on here.

the links that are added in the "issue links relates to" like JIRASITE.ca/browse/IT-2222 are not working, but the links that are like JIRASITE.ca/servicedesk/customer/portal/10/it-2222 are working fine.

what this tells me, is that front end "issue links - relates to" links will never work and have never worked! for customers.

i think i just need to make jira create the correct kind of front end links here.

[JiraYo]

the extensions for jira service desk people clued me into whats going on here.

Because the agent is part of jira-servicedesk-users group, jira treats them as if they are an agent on ALL the projects. So all the links render for them as backend links.

I have about 10 different projects. I have agents that are only agents on one project. I am asking divinity whether there is some sort of other workaround here, to allow an agent on one project, to still be a customer on all the others. There is not enough silioing of permissions it seems.

There is a real hard separation between customers and agents. Expanding as far as the way that jira presents and renders links. interesting, and yet depressing as i will probably have to grant browse permissions to all sites for the 3 agents that are on this one project. really sucks.

[Marty]

Hi,

I am not on the Jira team but I will try to help.

Is it possible to run the workflow as a non sysadmin user?