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

@ 879378878e7f

This works only for Jira Cloud. Is there a plan to bring it to Data Center?

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.