983
Customers have installed this app in at least 983 active instances.
by Atlassian Labsfor Jira Server 7.6.0 - 8.6.1 and more versions
Versions available for Jira Server 5.2.9 - 7.5.4
Unsupported
This app isn't formally supported.
Unsupported
This app isn't formally supported.
Unsupported
This app isn't formally supported.
Get it nowFree app
Automatically creates Issue Links
Automatically creates Issue Links
Automatically creates Issue Links
Mention issue
Link automatically created
Easily tell issue was mentioned
User mentions issue in comment.
Link to mentioned issue is automatically created.
In FP-1 user can easily tell that it was mentioned in FP-2.
More details
There are no additional details.
Reviews for cloud
(19)Sign in to write a review
This plugin has been great for us, except for that it does not pull from custom fields. I though it did this in the past before we upgraded to 7.1. Is this going to be a feature that will ever be added?
Great Add-on i used previously on JIRA-Server, but not supported on JIRA Cloud which i use now.
This looks really handy, especially in a Service Desk environment.
Will it allow linking to another instance of jira which is connected via OAuth application link?
It would be really useful to be able to specify a link type based on the field that the mention appears, as well as adding support for custom fields.
This plugin doesn't seems to work on Jira 7+ - is there any plans to update?
Version 1.2 supports both JIRA 7.0.0 and 7.1.0.
Reviews for server
(19)Sign in to write a review
it would be nice if, apart from issue key, it could recogize full url of issue link (plain text and hyper link).
it's would be more popular, more convenient to insert issue url than just the issue key in discusion because poeple ussually open that url/ link and then copy/ paste
Can you please release support for Jira 8.2.x thanks
The plugin is great! It works exactly, and is a massive timesaver. we really need it. How about support for JIRA 8.1.x? Thanks.
Handy for understanding how issues link to each other organically based on discussion.
Would be much more valuable if it could also automatically link based on people copy/pasting full JIRA links into comments.
ie) PROJ-123 and https://example.com/browse/PROJ-123 would both auto link tickets.
I really like this plugin, but I need something similar which is maintained.
Reviews for Data Center
(19)Sign in to write a reviewThis plugin has been great for us, except for that it does not pull from custom fields. I though it did this in the past before we upgraded to 7.1. Is this going to be a feature that will ever be added?
Great Add-on i used previously on JIRA-Server, but not supported on JIRA Cloud which i use now.
This looks really handy, especially in a Service Desk environment.
Will it allow linking to another instance of jira which is connected via OAuth application link?
It would be really useful to be able to specify a link type based on the field that the mention appears, as well as adding support for custom fields.
This plugin doesn't seems to work on Jira 7+ - is there any plans to update?
Version 1.2 supports both JIRA 7.0.0 and 7.1.0.
Cloud Pricing
Server Pricing
Data Center Pricing
Basic support resources are available for this app.
Vendor support resources
See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 1.3 • Jira Server 7.6.0 - 8.6.1 • Released 2019-01-31
Summary
Add support for Jira 8.0.0
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate AutoLink Plugin for Jira via search. Results include app versions compatible with your Jira instance.
- Click Install to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
To find older AutoLink Plugin for Jira versions compatible with your instance, you can look through our version history page.