Subtickets of an epic are grouped together in the kanban board

This question is in reference to Atlassian Documentation: Configuring Columns

Subtickets of an epic are grouped together in the kanban board. Can I shut off this feature so tickets can be prioritized regardless of epic? 

3 answers

0 vote

Hi Amanda,

My guess is that your kanban board currently has swimlanes based on epics. This is what is probably the cause of the grouping.

To verify whether this is the case and undo it, go to the configuration of your board. Then, from the options on the left select swimlanes:

Screen Shot 2016-10-06 at 17.50.56.png

Probably you will see 'Epics' selected as an option here. You can choose a different grouping option or switch to no swimlanes at all to see all issues on the same board without any horizontal grouping.

Be aware that though that this change impacts everyone using the board.

I should clarify. The tickets are grouped together by epic in the columns. I am not using any swimlanes on this board.

In the image you can see the highlighted ticket is a subticket of a parent/epic named "homepage" but I cant make it a higher priority than the epic above it "account and settings". in fact all tickets that are part of an epic cannot be manually ordered at all. tickets not part of an epic can be vertically moved around to indicate priority but tickets in an epic can only be shown in numerical order. whats up with that? 

Screen Shot 2016-10-06 at 4.54.35 PM.png

0 vote

Hi Amanda,

I guess that you will normally not be working on the epics themselves. Could you try modifying the source of your kanban board to exclude the epics?

I modified the filter of the board to exclude epics but it still groups subtickets by the parent ticket. is there a better way to accomplish what youre describing? 

There's one thing that immediately comes to my mind; could you check whether ranking is enabled on your board? You can check this in the general configuration of the board or you can explicitly add 'ORDER BY Rank to the end of your JQL statement - given it isn't there yet already.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,316 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot