If anyone on datacenter is looking for solution, we are using at eBay this tool to simplify our life and have links per projects  
I still don't get it why it is not out of the box. It is what it is  
https://marketplace.atlassian.com/apps/1214172/extended-schemes-for-jira?hosting=datacenter&tab=overview

Cheers!

We would love this please. We just merged instances and now have 40+ types covering multiple companies and work types. Restricting on a per project or user group basis would be great.

+ would be nice to be allowed to decide what issue link types I can allow per each project

Hello Atlassian Team,

This issue is really demanding. Already additional add-ons exist to fix this request.

I think it is time to implement this feature!

Atlassian team, please, save my pointing finger from being tied by scrolling unneeded linking types!

Best regards,

Ievgen Kovalov

+1   our Service Management and Software projects require very different links and restricting options would make this option a lot more user friendly.

This is very very painful. The list of possible links is increasing every time when a different branch of our huge organization joins in and adds their own linking schemes that suits to their workflows. Now we have over 30 linking types and I just heard that it will significantly increase in near future.

It's annoying to start printing guidance lists of preferable links inside projects for the employees. This really slows down our workflow and increases the demand for documentation, supervision and schooling.

How many votes does this take to get this on the roadmap?  Obviously it has gathered enough interest to be considered.  Might not be a low hanging fruit type of issue but would obviously please a lot of users to get this done!  

I'm relocating my project from an instance where I have total control, to a much large instance with scores of projects in, and I've been told I can't use the link times my projects are used to.  This means changes to our working procedures, and issues with closed linked tickets.

In 2015 the following comment was made

• "While this issue is not currently on our roadmap, we do hope to address it in the future."

It's now 2023:  can we have an update please?  

I think I can see that inter-project linking would be a challenge to come up with "one right way to handle all customers' scenarios".  However, I believe a reasonable solution would be: only allow "relates to" or "requires" when linking inter-project, and then warn admin if they attempt to delete these from the project that inter-project linking won't work thereafter. I believe that is a reasonable "compromise" that the vast majority of customers would settle for, especially since the alternative is apparently to be without any option for years and years. 

What does it need to have this request implemented? The ticket was created in 2009. I think this is no rocket science and could be done quite easily. Please, take this on the roadmap for the next (minor) release.

Thanks & best regards

Mark

Some Jira admins suffer from the sins of the previous Jira "admin."  We need either this, or, to deactivate link types so that the old ones are still there in the old badly configured projects, and other teams do not continue to use them.  

SEE BELOW REGARDING INFO FOR THIS TICKET!

Hi everyone, we at veniture have created an app called vLinks - Easy issue linking. It offers creation of a JQL filtered custom field that allows you to link issues(and confluence pages) and have them synchronized with Jira issue links. 

It support all Jira default issue link types and custom link types too. 

Most importantly(regarding this issue) we provide Issue Linking Schemes. Users can define which link types will be used per projects.

See "Issue Linking Scheme" under the documentation:

https://app-documentation.atlassian.net/wiki/spaces/AV/pages/1109327910/Administration+Guide

I just voted to increase gathering interest counter to this issue created 13 years ago. @Atlassian: yes! - I do wait for this feature, too!

I can't believe this feature never made it into Jira.
I'm doomed to whatever link types are specified for the entire Jira server? This induces clutter galore. And completely against the design approach of Jira - which (as I understand) is to flexibly specify schemas for what you need for your project.

This is a much-needed feature if your organization uses multiple Atlassian products. Service desk, it support, and dev all use different issue links. Having them all appear in every project makes the feature quite cluttered and not an enjoyable experience.

How is this still not in?
We can add so many schemes to projects, why cant we limit what links a user is allowed to use...
Bigger Environments with several thousand users have sometimes the need to have many links available for certain projects but they are not needed or should be limited to certain users within a project.

+1

+1

This is a real issue now that you're making everyone switch to your cloud version where add-ons can't modify this functionality.  Please fix this issue.

Please add this feature.  Users are confused when seeing all links available in the instance.

This needs to be fixed please!

As mentioned by Julius Zatroch in the previous comment, the only problem for the referenced add-on is that it only supports Jira Server (which will reach EOL and dropped by Atlassian in the next few years).  For add-on to be viable, it has to be certified to support Jira Data Center and Jira Cloud by Atlassian.

Best, Joseph

Lets check this addon:   

Extended Schemes for Jira

https://marketplace.atlassian.com/apps/1214172/extended-schemes-for-jira?hosting=server&tab=versions

We have many users/projects requesting this capability.  Would be extremely helpful to have this feature.

This issue is duplicated by several other issues.  Can someone at Atlassian take some time to consolidate these into a single issue or at least one for CLOUD and one for SERVER. Currently this request goes back to 2009 and having duplicates dilutes the votes.

I would add that splitting feature request between server and cloud does not seemt to make any sense. I understand that occasionally this makes a difference in implementing a solution but when gathering interest for a new feature this differentiation does not matter. Plus all CLOUD features work in SERVER it's only in the other direction that there is some feature gaps due to security. When a feature is implemented in SERVER and not CLOUD then you can clone the SERVER feature issue and mark it as will not implement.

Here are the ones I found with a few minutes of searching there may be others.

https://jira.atlassian.com/browse/JRACLOUD-36494
https://jira.atlassian.com/browse/JRASERVER-36494

https://jira.atlassian.com/browse/JRASERVER-16325
https://jira.atlassian.com/browse/JRACLOUD-16325

https://jira.atlassian.com/browse/JRACLOUD-8497
https://jira.atlassian.com/browse/JRASERVER-8497

https://jira.atlassian.com/browse/JRACLOUD-59123
https://jira.atlassian.com/browse/JRASERVER-59123

https://jira.atlassian.com/browse/JRACLOUD-42181
https://jira.atlassian.com/browse/JRASERVER-42181

+1

We have several hundred users.  They are simply not disciplined enough (or they're trying too hard to solve a problem for themselves that already has a solution) to restrict themselves to using only certain link types in their projects.  This creates havoc in some of our Structure boards that use the linked issues to extend/group.  Need to be able to restrict link types by project (at minimum) or, ideally, by issue type.  Seems like an obvious need, but these requests go back more than 10 years now.

I would expect to be able to do this using the ScriptRunner plugin

People tend to choose wrong link types because they see all the link types in every project. We have a lot of projects with different needs, hence many link types. This makes filtering on link types challenging.  

+1 to this ask. It would be great if project admins can set this themselves.

totally necessary

Please implement this very important tooling

Yet another great example of a request <2010 with quite clear use case and community interest.

Can we have an update if this ever made it to the roadmap?

really need this done as currently its unmanageable!

At least, please implement a facility to be able to show or hide "Issue Link Types"

Please, implement it !!

Please implement link type schemes.

kkkkkkkkkkkkkkkk

Thank you Atlassian for laughing at us for the last 10 years.  Yes, we know it's your software and you know what's best for us. Excuse us for thinking your developers and your mission statement writers actually communicated with each other.  We also appreciate the resolve it takes to completely ignore your customers....we're sorry for pestering you for scraps of common sense functionality.

Please, implement it

Yes please implement this.  Scrolling through unrelated issue link types in the various projects is the mostpul thing in JIRA. 

Yes, please add. Scrolling through unrelated issue link types in the various projects is a pain. 

We have a user base of 2000+ and 50+ projects. Would make it much easier to handle those. Please consider for implementation.

I would hope that it would be implemented as next, after we got priority schemes in Jira projects.

No official update since 4 years. Do we have any plans to implement this?

+1
We have a user base of over 4000 and have received this request multiple times. Please plan to implement.

Is this Issue still in sight?

We have a few customers with this requirement.

It would enable us to stop users from working with unwanted link types. Important when working with Structure for Jira.

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

+1 but i would love it, if it would be possible to configure issue links per issue type.

+1 My Team/Project would also appreciate if we were able to reduce the number of Link-Types between Issues just like you are able to reduce the number of Issue Types pro project.

+1 We would very much like to see this feature implemented as this seems to be highly interesting for many customers. A stepwise implementation for different limitations (per projects, issue type and so on) would be appreciated as this feature should be available as soon as possible.

+1000 I'm realy looking forward to this feature and i have to agree with SABVARX. We actually have many link types. Most of them are for all projects, but some of them are special links, which describe how issues between project a and project b work together.

Issue link types should be configurable in Schemes, as it is for fields/screens/... They should be configurable per project AND also per issue type.

+1 Jira can be our Swiss Knife in company, not only for bug tracking. This requires a seperation for link types per project simular to all other parameter (screens, workflows, issue types). This means also more users to license .