Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,360,707
Community Members
 
Community Events
168
Community Groups

Linked Issues Swimlanes?

I currently have a JIRA Agile board, and I am trying to create a JQL query that will show all the linked sub-tasks under each parent task.

 

I know the JQL query: issue in linkedIssues("MFA-6")... will allow me to see all the sub-tasks under the parent task "MFA-6"... however.. what JQL query can I write that for each parent-task (swimlane) below will show it's sub-task?

issue in linkedIssues(<ALL?>)

1 answer

1 accepted

0 votes
Answer accepted

Hey Cierra,

You actually may not have to edit the JQL at all.

Under Board Settings if you go to the Card Layout section you can add Sub-Tasks to both the Backlog and Active Sprints views.

This will show any linked Sub-Tasks under the issue without any JQL changes.

Hope this helps,

Tyler

This is actually a great and less tedious alternative! Thank you!

What if you aren't using SUB-TASKS, because the Burn-Up reports don't report completed Sub-tasks as "completion" (which if it was working the way it SHOULD, it WOULD)?

 

How would one do that.

Story

^^

||

|| Relates to

||

\==== Task

||

\==== Task

 

How do we monitor progress when Jira operates so illogically. If you're going to have Swimlanes to monitor Story progress by viewing Sub-tasks in the active Sprint, then support reporting the Burn-down or Burn-up via counting sub-tasks.....Sheesh!

Yeah I agree. Would be great to have burndown based on sub-tasks as currently this swim lane setup only works for Kanban teams but is not much help if you are using Scrum and want to report on progress within sprint. 

 

I'm using Technical Stories at the moment that I link to the user story and assign story points to. However if I wanted to see the related Technical stories and parent stories in a  swim lane I can only do it by manually creating JQL queries for each parent story and basing my swimlanes on these. This is just not right...   

Like # people like this

Yes...it's just not right, is it.

@Reka, this is exactly the issue I am facing. Business create stories which the technical teams estimate and decompose into smaller tasks. To date I have used sub-tasks as the logical currency to deal with. This works great as we can see exactly what needs to be completed on order to deliver a particular story. We visualize stories as swim lanes on our board.

The problem lies in that our devops guys deploy in technical story "currency" and this is consistent across the firm (per technical platform). Rather than taking a Canute like approach it would be sensible for us to decompose into technical stories and replace the subtasks on our board with these.

Supporting such visualization with JIRA seems close to  impossible!

Like Marcelo Lopez likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events