Issue Summary

For projects that are "read only" (no issue linking permissions), there is a difference in outcome for issue link creations and it comes down to whether the link is an outward or inward link.

Steps to Reproduce

1. Create two projects. Project_A and Project_B with specific permissions.
   • Configure Project_A to allow users full permissions (edit issue, issue linking).
   • Configure Project_B in a way that nobody have issue linking permissions.
2. Link some issues from Project_A to Project_B. For eg:
   • A-1 links to (outward) B-1.
   • A-1 links to (inward) B-1.
     Both links above would be on the same link.

Expected Results

Expected no issue links can be created. Or, both links can be created.

Actual Results

• Outward links can be created.
• Inward links cannot be created.

When link cannot be created, we see the following:

We also see from HAR analysis, HTTP 401:

{"errorMessages":["No Link Issue Permission for issue 'B-1'"],"errors":{}}

It is also noted for links types that has the same outward and inward, it would always fail.

Other notes
Discovered that this inconsistent behavior (whether link is outward or inward) happens due to the issue linking API:

• https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-links/#api-rest-api-2-issuelink-post

Specifically:

Link issues project permission on the project containing the from (outward) issue.

Workaround

Workaround not applicable. Requesting for consistent behavior.