Jira links not working
See original GitHub issueThe feature that turns JIRA ID’s in the body of a PR to links has not working for us since the 25th. This is probably related to https://github.com/atlassian/github-for-jira/issues/657 and https://github.com/atlassian/github-for-jira/issues/658, both of which happened around the same time.
We are on version 1.1.6-AC of the Github for Jira
Jira app. I don’t see any “update available” badge.
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
external link on Jira comment not working - Atlassian Community
Running Jira Software 7.13.3 When I'm adding comments to a Jira issue, and I want to link to an external url, I'm always...
Read more >Link issue button not working - Atlassian Community
We have the issue linking turned on, the permissions set properly for linking issues, and the linked issues field is added to the...
Read more >Link an issue | Jira Software Cloud - Atlassian Support
Open the issue that you want to link to. · Select more (•••) > Link > Jira Issue. · Choose the relevant Jira...
Read more >What are possible reasons why I can't link issues?
It could be that you don't have permission to link issues. Please check your permission scheme under the topic, Issue Permissions.
Read more >Can't Link issues - Atlassian Community
Is the issue you're linking from in the same project as the issue that you are linking to? Perhaps you lack permission in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@rachellerathbone I did a full sync, I’ll let you know if it happens again.
Closing this issue since it was resolved. Please check @thombergs ’ comment above for details.