-
Suggestion
-
Resolution: Unresolved
-
1,370
-
61
-
Hi everyone,
Thank you for taking the time to share your valuable feedback with us. Your input is greatly appreciated, and we understand the effort and dedication it takes to provide us with your thoughts and ideas.
At this time, we regret to inform you that the specific functionality you’ve requested – the ability to assign different issue link types to individual projects – will not be prioritised in our near-term roadmap. While we recognise the potential benefits this feature could bring to your workflow, our current focus is on areas that impact the largest number of users, such as performance ease of use and enhancing the overall user experience with the broadest appeal.
We recommend exploring a few powerful apps from the Atlassian Marketplace that may offer the flexibility you're seeking. For example, Issue Matrix provides an enhanced way to manage and visualise issue links across projects, while Linksy offers additional functionalities for handling and optimising issue links. These solutions may provide the control and visibility you're looking for.
Thank you again for your continued support and understanding!
Ahmud
Product Manager-Issue View
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
This is a routine update of this issue.
We are working to make JIRA more flexible on a per-project basis so that it's easier for a variety of teams to adapt it. Issue links certainly fall under this category. While this issue is not currently on our roadmap, we do hope to address it in the future.
Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
JIRA Product Manager
Allow to select which issue link types apply to which projects.
- details
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Future Consideration
- is related to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
ENT-2903 Loading...
- relates to
-
JRACLOUD-79682 Issue create allows linking issues from a project with no issue link permission
-
- Closed
-
-
- Closed
-
- Closed
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-16325] Customise Issue Links per project
Hello everyone ,
I used a plugin and it was very helpfull for me to create link types for each project in my instance .
It's very simple to use with good user experience .
I could see not having this if an "Issue Picker" field existed.
Given that the Priority field is finally getting the schema/context treatment I still have hope for this.
@karim,
Yes I am aware of the limitation.
My point is that the product does not actually meet the requirement of the request to prevent the ability to create links of certain types. Adding a separate section where the link types can be restricted is not the same as preventing or modifying the user of the built in Link Issues functionality. The users can still create links of the the other types.
@atlassway
Your app does not appear to entirely restrict which link types can be used in a project. The Link Issue button remains available in the issue details view, and with it a link of any type can be made to other issues.
It is only when one uses the Enhanced Links button/section that the types of links available are restricted, but that only restricts the link types within the Enhanced Links section.
Please clarify how your app prevents users from creating issue links of other types.
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.
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.
This causes a lot of issues for enterprise users that have 5000+ active users. The list of custom link types is massive across the organisation as such it's so error prone for teams to find and use certain link types.
955fddd47a93 added a comment - 2 days ago
HI everyone, there is plugin called extended-schemes-for-JiraI believe it does excaly that but of course it's not free. Atlassian should make free these "system utilities"
https://marketplace.atlassian.com/apps/1214172/extended-schemes-for-jira?tab=overview&hosting=datacenter
Cloud availability
A cloud version of this app is currently not available.
Contact the vendor to let them know that you are interested to try this app for cloud.
HI everyone, there is plugin called extended-schemes-for-Jira
I believe it does excaly that but of course it's not free. Atlassian should make free these "system utilities"
Guess I missed that part Dana - 2009! Just close this and tell us it won't get done
Shiela, traction? I’m trying to think of a good joke here…
Have you seen the submit date? This has about as much likelihood as happening as… I don’t know you fill in the blank.
Gathering Interest since 2009? WOW!
Atlassian, it is time to do something about this, isn't it?
Bruh, 14 years almost? Is this ever going to happen for cloud????????????????????????????????????????????????????
We have multiple projects with different specs. This feature is a MUST for us. Please add it soon.
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 not having this feature is completely against the design approach of Jira - which (as I understand) is to flexibly specify schemas for what you need for your project.
Please add this soon. Thank you!
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.
Its been 12+ years since this issue was created (23/Jan/2009 1:26 AM)??? 
I hope they add this option soon.
I agree. E. g. the use case to distinguish link types for Jira Software from Jira Service Management
With so many different types of projects and workflows, issue linkage should also be customizable and restricted based on Issue Schemes. It's high time this feature is implemented.
I'm probably restating the obvious, but want to make sure the my "why" is heard. For the most part Jira service management has been excellent in allowing me to develop a workflow that is intuitive. I have minimal documentation and the team gets on pretty well with it. However, the linked issues types is pretty annoying from a support standpoint. My support team has to scroll through the developer focused linked issues types ("blocked by" is a good example). I'd love to just have the 2 I need; causes and relates. I agree with the other commentary. A linked issues scheme which can be assigned by project makes most sense.
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
No plugins should be needed. Link Type scheme per project is needed IMO. I am stuck with a system that had 18 link types. Of course the should never have existed due to this limitation we cannot remove them since they were used in old workflows. So, the only fix would be merging them to few types (hard to get people to agree to that).
So, a simple link-type scheme (much like issue types) per project could fix this issue.
This plug-in does not seem to be for the Cloud instance of Jira - is there one that is? I just want to be able to add another dropdown in the link field.
Support [Develocenter]
added a comment - 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
Support [Develocenter]
added a comment - 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 
Roland Bürk
added a comment - +1 but i would love it, if it would be possible to configure issue links per issue type.
Roland Bürk
added a comment - +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 
.
We have the same situation as Slava (above) we need to be able to have different link types per project.
Slava
added a comment - +1 After multiple acquisitions our Issue Linking list is quite long even after consolidation as different departments require different link types. Would be great to filter list per project.
Slava
added a comment - +1 After multiple acquisitions our Issue Linking list is quite long even after consolidation as different departments require different link types. Would be great to filter list per project. 
Wolfgang Fellner
added a comment - +1 would be great!
A useful feature! +1