swimlanes story linked issues

[Steve Iribarne]

I've read a ton of different post but I can't seem to find the right thing...

I am using Jira Cloud.

I want my swimlanes to be like we display on my JIRA board (physical) where I have a story, and then a bunch of tasks bunch in with each story....

Like this:

Story -- foo

         task1

         task2  

                                      task3-> in progress       

                                                                                task4-done 

Sorry about the ascii art... 

I think I can do it with linkedIssue and an JQL query but maybe I can't.  Please help.

[Deleted user]

issue in linkedIssues("p-984")or key = p-984

Is the query I use for my swimlanes.  This is because we have items in other projects we have to track in the lane.  I only wish I did not have to maintain the issue id's

[Peter Jones]

I have a very similar situation (multiple projects) and want to show parent tickets as swim lanes and child tickets from another project within those lanes. There's no way I am going to maintain issuekey's manually though!

[Aron Gombas _Midori_]

I think, at the moment, out of the box, in Jira there are 2 ways to express parent-child relations and visualize them in board swimlanes:

1. Story <-> Sub-task
2. Epic <-> Story

If both are sub-optimal for your use case, you may need to check out the apps that could open new options.

[Deleted user]

Which is the point of the request.

Jira's use of "Sub-Task" is broken in the way a Scrum Team most ideally would utilize the metaphor.

If it were, then "Burn-Up" or "Burn-Downs" would track using Sub-Tasks, just as you can use "Issue Count" 

Either that, or it would allow you "Group By" "Relates to" and allow you to visualize swimlanes that way.

A swimlane by "Relates to" between Story & Task (without having to specify the TARGET ) would also allow one to visualize this more appropriately.

[Kian Stack Mumo Systems]

Steve,

Have you considered using Subtasks to solve this issue? If you use Subtasks underneath a story, you can configure  Swimlanes based on Stories.

https://confluence.atlassian.com/jirasoftwarecloud/configuring-swimlanes-764478010.html

Thanks,

Kian

[Steve Iribarne]

Subtasks don't work for us because the view is limited.  The idea is to use JIRA just like I was using it after taking scrum master certification training.

That is, we have a story, then when we are doing our backlog grooming, with stories that are going to be added to the backlog, we want to create a list of tasks for that story (based off of our definitions of done) and then during our standup's we discuss the remaining time on each of the tasks.

Subtasks can sort of work, but there is something funny that goes on with the burndown and burnup reports essentially making them useless.  At least from my point of view.

So my question still stands:

I want a board that will have swimlanes based on stories and then in each story all related linked tasks.  

What's mind boggling is that I've seen tons of people asking for this and you'd think there would be an easy solution today (without having to use external marketplace plugins).  

But if I have to I will.

Thanks for any info you can help me with.

[Deleted user]

Yes one more instance where Jira doesn't support Scrum.