Try out Enhanced Links for Jira  to customize Issue Link Types per (Project ,Issue type or other criteria) using JQL expressions .

Enhanced Links for Jira allow you also to :

• Bulk Update Issue Link Types
• Bulk Delete Linked Issues via bulk change .

There are some more useful features like :

• Edit Jira Linked issue fields in list view.
• Enable coloring for Jira issue link types .
• And more ...

Stay tuned : New feature will be launched soon : Control visibility, display order, and usage for Issue links.

Documentation !

Questions? Ask us any time , or send us an E-Mail to support@atlassway.com and we will get back to you as soon as possible.

Please fix this basic feature. Its really annoying TBH.

PLEASE make this happen!!!!

I am surprised this is not possible already.

I am not associated with this plugin at all, but this seems to do what I want for others looking:

https://marketplace.atlassian.com/apps/1215311/stagil-assets-advanced-links?hosting=server&tab=overview

We utilize server currently - looking to go to Data Center in the future most likely. This feature is critical to us. We have many issue link options available that need to apply to a single issue type - for example, while on a new Feature Request a user can create a "has risk of" link to another issue - that issue should be of the Risk issue type but Jira displays bugs, stories, etc. in the dropdown to select the Risk. We have in some cases done custom fields/code to prevent this but doing this for all our issue types would be a bit overwhelming. It would be nice if when defining the issue linking you could select what issue types apply on the incoming and outgoing ends of the type. 

For example

Name     Outward Desription    Issue Types                    Inward Description     Issue Types

Risk        has Risk of                 Feature, Story                is Risk of                   Risk

When this is defined and the user is in a Feature and selects has Risk of it would display only issues of type Risk

vice versa if on the Risk and selects is Risk of the select dropdown would show Features and Stories.

I really don't understand how this can be marked as Resolved, seems to me that until this is actually supported it shouldn't be marked as Resolved.

Thanks,
-Glenn.

When will these add-ons be available for Cloud instances?  Thank you.

Hi there,

maybe this free addon I made can help: [Easy Links for JIRA|https://marketplace.atlassian.com/plugins/com.codedpoetry.easylinks.easy-links/server/overview.] It provides two new custom field types that manage behind the scenes the issue links. You can also restrict the available values of the fields with JQL expressions.

Regards, Fernando

Hi,

we are thrilled to announce that we have just released Links Scheme add-on which allows to manage Link Types for Issue Types and Projects the way as you always expected.
Please try it, we would love to hear your feedback.

Regards, Develocenter Support

Trigger works

Martin, you've resolved this issue as "Answered", but I think "Won't Fix" would be the more correct choice, and it would allow us to query for these types of requests in future.

Many thanks for reporting this issue, however this is not something we plan to add to JIRA at this time.

Regards,
Martin
JIRA team

If not possible to restrict the issue types in linking, at least please provide a possibility to filter the search by issue type?

I would also love to see this feauture in JIRA! We have a lot of different issue types (Change requests, issues, process documents etc.) and the issue type is only shown using the icon (when searching for issues to link to). This would be a killer feature...
/Aarto

This would improve the usability of our JIRA implementation significantly. Even at the relatively "young" age of our JIRA implementation (about six months) we are already seeing a tendency for people to make mistakes in the type of link they make between projects.

The usability issues are much exacerbated by the fact that you cannot simply edit the link type - you have to actually DELETE the link and re-create it again. This is a really painful process to go through constantly.

I hope that helps to add some colour as to why this feature would be valuable to us.

Thanks.

This is still an issue for us, discrete links with defined ends would be a great opportunity for us!!

I have developed a plugin that implements restrictions in the form of workflow conditions and validations, to restrict the issue types allowed to be linked for a certain issue link type. It also restrict the status of the issues, and can also restrict the issues to belong to the same project if desired.

https://plugins.atlassian.com/plugin/details/29496?versionId=29497

I hope it helps,

Fidel.

This would be very helpful to us. We use links extensively and have many different types, but only several pertain to any particular project. Our list of link types is quite long and error prone to selecting links that don't apply to the current project.

An "Issue Type Link Scheme" that could be applied to a project would be very very useful (if supported by edit/search capability). (I imagine it would probably be composed of discrete Link Schemes)

Currently the links are very freeform - yet they are a critical piece of metadata for some of our operations e.g. linking a production problem record to a bug. This is a problem where some users might create inappropriate links, and we can't even create a simple filter based on Links in order to do sanity checks.

Thanks for the clarification. I hope you do not mind, but I put the summary into JIRA speak for easier searching.

Sorry for the delays in responding
I would like to limit the types of relationships that can be made between specific

I would like to be able to define that a
'supports' relationship
can be from a 'requirement' to a 'task'
can be from a 'enhancement' to a 'task'
'duplucateOf' relationship
can be from a 'bug' to a 'bug'

etc
so I would like the system to limit the choices available to the UI, and restrict the issues type that can be linked.

Hi Michael,

Do you mean that you would like to restrict what Issue Links type appear on certain issues? If so, on what criteria should the restriction be made?

Or would you like to resrict what issue scan be linked together? If so, how would you like the restriction to be specified?

Thanks,
Anton