Task-board appearance: Two statuses in column?


Where I work tasks can have the following statuses (that the end-users see):

To Do, In Progress, Done, and something of a joker in the form of "On Hold". As you are probably familiar with issues ideally flow from left to right, going from To Do -> In Progress -> Done. However On Hold really breaks the flow. See this picture of our board:


I don't see a problem-free place for the "On Hold"-column. Tasks may "jump" back and forth, left and right, wherever you'd place it.

The solution I can think of is to have "In Progress" and "On Hold" share the same vertical space, as described in this sketch:


Can the above appearance be configured?

3 answers

Hi Will,

You could try the following trick with swimlanes :

  1. Go to the configuration section of your board (select the configure option next to the cog on the right top side of the board).
  2. Go to the columns tab and move your In Progress status and your On Hold status into the In Progress column.
  3. Go to the swimlanes tab and select Base Swimlans on Queries.
  4. Create 2 swimlanes called On Hold and In Progressand give them the following queries:
    1. On Hold swimlane : status = "On Hold"
    2. In Progress swimlane : status = "In Progress"

You should now have an overview of your board with your on hold issues clearly visible in a seperate swimlane, it's not exactly what you want but it comes close.

Best regards,


I believe that additional columns can't be added on top of an existing one, Will.

Correct me if I'm wrong, but isn't the Task Board meant to have the columns adjacent to each other in the flow you've mentioned:

To Do > In Progress > Done

But if there are any issues/impediments along the In Progress column, you would add them to the On Hold? Unless your use case is a bit different.

I want the same thing but instead of having 2 status one below to another I want both to be one next to the other.



Status 1 | Status 2

If you want that, why not just have two columns?

I just want one "In progress" column. The reason is that an issue that is not on the test server (Ready to test) is a issue "In progress". The dev team asked for a column to move the tasks that have been completed in their machines but they haven`t pushed it.

Sounds like 2 columns! Actually, I'd consider two boards. One for Dev, one for test. Different views.

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 ...

2,853 views 12 18
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