-
Suggestion
-
Resolution: Unresolved
-
29
-
23
-
NOTE: This suggestion is for Jira Cloud. Using Jira Server? See the corresponding suggestion.
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that this one deserves more of our attention, however we haven't decided yet if we're going to implement it in immediate future.
We'd like to better understand your needs and get know how many of you see this useful, so I'd like to encourage you to share feedback through comments on this suggestion or Atlassian Community and vote, so we know the importance of potencial change.
If you're interested about latest updates and upcoming plans, please check out the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
Regards,
Michał Tomasik
Software Engineer, Jira Cloud
Issue Summary
With the addition of the JQL function issueLinkType, Jira Cloud now has the ability to let users search by the issue link's Name, Outward Description, and/or Inward description. The problem with this is that by default the issue link type 'Blocks' also has an outward description by the same name 'blocks'. Since these are the same, you can't actually only get back results with that outward description. Instead you get back all issues with that link name, which includes both outward ('blocks') and inward ('is blocked by').
By default only the Blocks link type has a description with the same value as the link Name. The suggested solution would be to have new Jira sites use a different change the outward link name from 'blocks' to something different such as 'blocking'.
Steps to Reproduce
- Link one issue to another with the blocks issue link type
- Search JQL with:
issueLinkType = "blocks"
Expected Results
Would expect to only get back a single issue with that outward description of 'blocks'
Actual Results
You actually will get back all the issues of that link name (both inward and outward description) because the term that is being searched here matches the link name.
Workaround
You can edit the link descriptions so that they do not exactly match the name of the link type. For example you could change the outward link name from 'blocks' to something different such as 'blocking'. This would at least permit users to make these specific JQL searches based on the description and not the name. Changing the link type Name will not prevent JQL from returning the issues "Blocked by", only changing the Outward description will.
- is blocked by
-
JRACLOUD-91509 Can't change default link type as it is recreated after a while
-
- Closed
-
- was cloned as
-
- Gathering Interest
[JRACLOUD-73372] Issue Link names should be different from their descriptions
Hello,
It seems possible to rename the issuelinktype from the admin UI.
Is it safe to rename "blocks" to "blocker"?
Please fix this one, i want to highlight on my board tickets that are blocking others, without the ones that are being blocked by.
issueLinkType = "blocks" includes both blocks and is blocked by
OMG, stupid unusable function; I do list all the issues which are blockers with all others which are blocked by those issues.
This is one fo the reasons the company will not use this functionality and will search for a different solution for the whole issue management.
I am having the same issue, and agree with Scott and Emily; I should not have to find an admin to be able to filter out blocking tickets. Will there be another solution for this issue?
Having the same issue. I concur with Scott Burat that you should not need to find a Jira Admin in order to be able to write a query to see what tickets are blocking others.
The fact that you cannot use "blocks" by default to generate as list of tickets that are blocked is a major flaw. There should not be a requirement to have the Jira Admin to define a new term for a ticket that blocks other tickets.
Is there an ETA for when this issue can be addressed as we need to be able to easily identify tickets that are blocked and tickets that block other tickets.
Ran into this issue today, 29 March 2021, 16 months after this ticket was opened.
I am new to using Jira so my question is simplistic. How do we display the value of IssueLinkType in a column of a JQL result?