Is there way to configure Swimlane Based On Initiative?

[Avinash Londhe]

Hi, 

As we can configure horizontal swimlane based on epics (to display stories) or stories (to display sub-task), can I configure them based on Initiatives(to display all epics under initiative)?

FYI, Initiatives are not listed in 'Swim Lane Based On' dropdown.

a) So is it possible to achieve this using query?

OR

b) Is there a way to add Initiative to list in 'Swim Lane Based On' dropdown

Would be more interested in answer to a.

This I want to achieve on Kanban Board. 

Regards

[Quinn Shanahan]

+1 this as a feature request. swimlanes based on initiatives would be great

[Tracy Hawker]

Seriously Atlassian, this is a critical product gap that has existing for way too long. 

[Alexey Matveev]

Hello,

b) is not possible.

a) possible but awkward. You would need to write as many JQL queries as the number of initiatives. It makes this solution too hard to maintain.

[Michel Meunier]

This answer is old. Is someone have found a way to do option A without having to do a JQL queries for each initiatives? 

[Diarmait O'Reilly]

I would love to be able to do B. Is it feasible, after creating new Hierarchy would like to use it to drive Swimlanes in Kanban Board

[Arnaud DESSEIN]

Yes me too, would love to do b. I have a board for run/sprint with stories organized in swimlanes by epic, and a roadmap board with epics and initiatives mixed with confusion where I'd prefer to have epics organized in swimlanes by initiative for clarity/readability. This would be more intuitive as all these levels of tickets are hierarchically related.

[Kim Dinh]

I would also want to do this for my sprint board.  We use initiatives for a lot of our planning. 

[Lorie Péron]

Hello,

Did one of you find a solution? I would like to do the same on my scrum board without having to do it manually every time there's a new initiative.

Thanks if someone have the answer :)

[Zora Vašulínová]

a)  query - issue in childIssuesOf("ABC-1234")

My colleague suggested this and it works for me :). But yes, it is to be manually maintained.

[Simon M]

The performance of this jql is horrible and frankly unusuable if you have a lot of initiatives and lots of child issues (epics and stories) in it. It is much faster to use a field (fieldXYZ = "Initiative ID/NAME").

For example we are using fixversion as a workaround and just with two swimlanes the loading time is half as much as with childIssuesOf().

Test with two swimlanes

childIssuesOf()

Test 1: 5.40s
Test 2: 5.62s
Test 3: 5.97s

fixversion

Test 1: 2.74s
Test 2: 2.99s
Test 3: 2.28s

I tried adding more than 10 initiatives and I had to wait almost 30s for it to load. The tradeoff is that in order to use a field you need to setup automation so the value will pass down to the childIssues. Otherwise it will be unmaintainable.

[Avinash Kumar]

Hi Guys,

Few people here are suggesting a workaround that, we need to write many JQL queries as the number of Initiatives. I am trying that. But in that case also, hierarchy is not coming.

In the swimlane, only Initiative is displaying. Epic(under that Initiative) and Story(under the Epic) are displaying in Everything Else swimlane.

Please help if have any solution. I really need it.

CC @Alexey Matveev

@Michel Meunier