Community resources
Community resources
Community resources
Linking Issues will require the "Link Issues" permission on both inward and outward issues
Hello Everyone,
As part as our ongoing efforts to improve usability and management of Jira Cloud, we will soon require the “Link Issues” permission on both inward and outward issues.
This will ensure the same level of permission is required on both issues. There are no changes to the issue-viewability requirements (e.g. via the “Browse Projects” permission key in Company Managed Projects) for linking issues.
What’s changing?
Starting 24 November 2025, Jira will require the “Link Issues” permission for all linking operations on both outwards and inwards issues. Previously, the "Link Issues" permission was only required on the outward issue. This change addresses a long-standing discrepancy in the permission level required for inward and outward issues.
An error response will occur if the user does not have the required permission while creating or updating the issue in the UI, operations via REST APIs, or automation rules.
Read for more details and impacted APIs.
Impact on existing workflows
Users, apps and automation rules that do not have the “Link Issues” permission on either inward or outward issues will be affected.
To ensure there is no unexpected impact, review the permission schemes and project permissions before 24 Nov 2025 and grant the “Link Issues” permission to the required users.
Impacts to APIs
Impacted backend APIs will throw a 401 Unauthorized if user lacks the “Link Issues” permission on either issue.
For more details, read this entry in the change log.
Contact
If you have any questions about this change, the best way to reach out is by leaving a comment in this community post.
If you have questions specific to your site, contact support.
Thank you,
Jira Cloud Team
Was this helpful?
Thanks!
Ahmud Auleear
2 comments