I use issue linking to handle dependancies between issues and would like to visulize if an issue is blocked in the backlog and kanban. Is this possible?
It does't really matter how I just would like to see and mabye (this is a bonus) filter out blocked issues.
I have searched but can not find any good solutions to this issue. I took a quick look at the ScriptRunner add on, but it felt overly complicated to solve something like this, I would expect this to be part of the standard product...
Edit made 19 March 2019:
With the release of Jira 8.0.0, you can now search JQL for linktypes natively, without the need for a 3rd party plugin. Details on this usage can be found in Advanced Searching - Fields - Issue link type. This new feature is also noted in the Jira 8 release notes.
I understand you are looking to find a way to visualize blocked issues in your JIRA instance.
Unfortunately, the native functions in JIRA's Advanced Search functions do not presently have a way to do this. That link explains there is a linkedissues() function, but that it requires an issuekey to return any results. There is not presently a way to show all the issues that have a link of type block natively in JIRA.
As you noted, if you were using the scriptrunner plugin with JIRA, then you could create a JQL filter such as
issueFunction in hasLinks(
Which you could then use to create a quick filter on an existing board to quickly show that information. This is documented in Scriptrunner Scripted Functions
Sorry there is not a better native solution in JIRA at this time. However there is a existing feature request in JIRA to add this kind of functionality natively, I would recommend watching and voting on https://jira.atlassian.com/browse/JRASERVER-25640
As of Jira 8, you can do this natively now. You can see that the linked suggestion ticket I referred to has been updated to indicate this in JRASERVER-25640
There are more complete details of how to use this in the reference document of JQL advanced searching: Fields: issueLinkType. In Jira 8 and higher versions you can now use a syntax such as
issueLinkType = blocks
in order to find issues via JQL that have a linktype of blocks.
One of the cool features in ScriptRunner was the ability to check the resolution on the ticket that is linked.
So you could query: project = TPS and issueFunction in linkedIssuesOf("resolution = Unresolved" , "is blocked by") which would show you issues that you have that are blocked, by an Unresolved issue. That way items would fall off the list as the linked issue that was blocking got resolved.
Thus you could infer that your issues, that was once blocked, is no longer blocked anymore.
Is there a way to do that with the new implementation of issueLinktype?
@James Alvir I don't have a clear time table on if or when this might come to Jira Cloud. There is a corresponding Jira Cloud feature request for this that is still open in JRACLOUD-25640 I would recommend watching that ticket for any updates to this.
Should this feature be implemented into Jira Cloud, I would fully expect that ticket to be updated to reflect this.
I may be misunderstanding the documentation but `issueLinkType` doesn't solve the issue of only displaying issues that have unfinished stories that are blocking it. The current feature set I believe only allows you to identify issues that have stories linked as "is blocked by", however, it is not possible to identify whether or not those blockers have been completed (aka have a statusCategory of "Done"). If anyone knows how to do this, please let me know! From my understanding, the current feature set is almost there, but currently still not incredibly useful. And I'm in quite a large organization, so don't really want to pay for a jira extension that's hundreds of dollars per month :/
If you don't want to go through scripting, it is not hard to do by exporting the data to spread sheet. Not good for all uses but good enough for some.
1) Use the standard search in Jira to find bugs
2) On the column selection for the result add "Links"
3) Export to csv, current columns
4) Open in spreadsheet
5) The links will be expanded into multiple columns
6) The first link column is: Outward issue link (Blocks)
I have to say that this is such a fundamental need on Kanban boards that I shouldn't have to program in JQL for the visual. Icon usage on the ticket/card is needed as a selection for the card. Period. No JQL. Put a little stop sign on the card with a hyperlink to the blocking issue or task. Something, or a roadblock symbol. Something VISUAL, not user code dependent.
As I use Jira and other Atlassian tools - it seems to me there is a general paradigm that the overall solution from the developers is that JQL is the answer. I'm sorry, this is a paradigm that SOME users simply do not come to your suite with. I am a relatively new user (about 10 months in)
Some of us come from a more traditional project management background and not an agile development background. Blocked and blocking is simply path setup and analysis that nearly every traditional project management tool on the market has a much simpler (and more calendar focused) view and modus that is visual in nature. In the really old days, where people only had Gantt charts, they still showed blocking with drawn in lines.
In MS Project you can create 'issues' on the network diagram, and then visually connect them together instead of memorizing their id numbers and hard coding it.
Searching - so much simpler in other tools where search is already context sensitive instead of requiring writing a line of JQL code to get the answer.
There would be a massive benefit to users like me (and I believe others that expect more visual manipulation of Jira) to have a mode of Jira that is decidedly more visual in nature.
I think the developers could build this on top of the existing modus of Jira without disturbing a single existing feature of Jira, but give a much more user friendly way to establish blocking/blocked by relationships.
What also would be excellent would be a visual report to show 'critical path' blocking of all issues in the blocking chain. This could get leaders to act more quickly to show them in one view if they don't handle the upstream blocking, their desired end goal that they really care about simply will not happen. 'Right to left' project planning and visualization.
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