Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I keep sub-tasks in their parent item's swimlane?

We organize our Kanban board into three swimlanes:

  • Highest Priority (based on priority)
  • Bugs (based on item type)
  • Everything Else

Our developers typically take an item (Feature, Improvement, Bug, etc.) and create sub-tasks which they then track through the development process. 

For tasks of Highest Priority items we can keep them in their swimlane by setting their priority accordingly.

However, for Bugs, we don't see any way to keep their sub-task in their parent's swimlane because the item type of a sub-tasks is 'Sub-Task'. How do we craft the bug swimlane so that it contains Bug items as well as their child sub-tasks?

1 answer

1 accepted

0 votes
Answer accepted

Hi @Yossi Geretz 

I am guessing that you are using queries for your swim lanes.

Without a scripting add-on, you would not easily be able to determine the parent item is a bug for the sub-tasks. 

As one work-around, you could use an automation rule to set either a label or custom field on sub-task creation, indicating the parent is a bug.  And then, change your swimlane query to search for that.  The rule could be:

  • trigger: issue created
  • condition: issue type is sub-task
  • condition: parent is a bug (perhaps using JQL)
  • action: add label to trigger issue indicating it is a bug-sub-task

Another possible work-around is to create a new bug-sub-task type, and then change the swimlane query to check for bugs or bug-sub-tasks.

Best regards,


Thank you @William Sheboy ! That was very helpful!

I created a label which we'll use for this purpose and modified the definition of the swimlane accordingly.

type = Bug OR labels = Swimlane:Bug

For now the assignment of the label is manual. As you suggestion, at some point we might automate this assignment, but even the simple manual approach is very effective, giving us the ability to keep our sub-tasks in the same lane as their parent.


Like Bill Sheboy likes this

Awesome!  I am glad that worked for you. 

When you are ready to take a look at creating automation rules is, here are some examples and documentation to help.

Like Yossi Geretz likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

153 views 3 7
Read article

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you