By using JQL using 1) issueFunction in hasLinks("is blocked by") or 2) issueFunction in hasLinkType(Blocks) one can get the list of issues that have this link.
And in the results the column "Links" shows the issuekey that satisfy this criteria. But the shortcoming is "Links" columns also shows issuekey that does not satisfy this criteria.
Ex: Result may show ABC-123 has "Links" ABC-345, ABC-456. But only ABC-345 is the right link that satisfies the link type = Blocks. ABC-456's link type =Depends.
How to narrow downs only those Links that meet a very specific Link Type. Ex: If I search for Link Type = Blocks, I dont want to see Links that dont meet this specific Link Type.
This is a good question, and seems like a deficiency in querying to me, that you can't manipulate the columns in any way... It makes links information in particular difficult to use at any macro level for exact reasons you outline.
One possible alternative is the Structure plug-in if you have it - there you can group by link / link type, so you can build a tree structure showing who's dependent on whom.
Hi Taduri, Kiran,
JQL is the responsible to narrow the issue impacted by the given query.
For those issues, will show the present value within any of the configured colums.
Links columns will always shows all links within the field regardless of the query, because the query only affects to the issues showing not filder the value on their fields in wany way.
hmmm what about something like this?
Supposing issues with "is blocked by" link have some constrains like project = myproject or status != done
You can query linked issues matching the 'is blocked by' criteria using this:
issueFunction in linkedIssuesOf('project = myproject and status != done', 'is blocked by')
Provided JQL should display linked issues which appeared before on "Links" columns, filtered by the given link criteria. However if you check the "Links" colums for these issues will display all links regardless of the given criteria since as I said before there is no way to filder colum data using JQL only matches issues.
The only alternative here is create a Calculated Scripted Field to dynamically show the 'is blocked by' issues of the current issue. Then, add that new field as a Colum in spite of the Links field.
You need some groovy skills to do that.
I've been struggling with the same kind of problem, to the point where I built my own app to solve it. This app allows you to specify a JQL query, limit the number of issue link types that get returned, and even create sub-filters to isolate certain projects/fields - https://marketplace.atlassian.com/apps/1221796/dependency-mapper-for-jira?hosting=cloud&tab=overview
...est practices. And don’t forget about the tried and true! Cloud Migration Center - central hub for all things Atlassian Migration Program. Includes links to our full resources page, s...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events