Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.3.1, 7.3.2, 8.20.2
-
7.03
-
8
-
Severity 3 - Minor
-
0
-
Description
Summary
User is unable to create linked issues in a project he/she is not an agent of. However, he can still link the issue manually from the project he/she is an agent of
Steps to Reproduce
- Create 2 Service Desk projects, project A (SDA) and project B (SDB)
- Create a user with JIRA Service Desk application access, and give this user the Service Desk Team role for project A (let's call him Dave)
- Modify the permission schemes for both project such that Application access: Any logged in user has Create Issue and Link Issues permission
- Create an issue in project A (SDA-2)
- Log in as Dave and access SDA-2
- Click on More > Create linked issue, create an issue in project B, with the linked issue being SDA-2
Expected Results
- Issue is created in SDB (SDB-2) which is automatically linked to SDA-2
Actual Results
The below error is thrown in the UI
Notes
If Dave is not meant to be able to create linked, the behaviour is inconsistent because
- Dave can still create issues in SDB manually (ie. SDB-2)
- Issue is still created although Dave is unable to access/view it after creation
- Dave can then access SDA-2, click on More > Link, and link this to SDB-2
- Although once the link is created, Dave is still unable to see this link in SDA-2 unless Browse Projects permission for project B allows Dave to see SDB issues
Workaround
- Grant Dave the Service Desk Team role for project B; OR
- Follow steps in Notes
Attachments
Issue Links
- is related to
-
JRASERVER-66682 Unexpected behaviors when linking issues remotely
- Gathering Impact
- relates to
-
JRASERVER-31248 Cannot restrict an issue linking using a permission scheme
- Gathering Impact
-
JSDSERVER-3426 Agents and customers experience problems when sharing links
- Gathering Impact