Map status from more than one workflow to JIRA Agile columns


in one of my projects we have the use case that we use two different workflows depending on the issue type. In future we want to use the JIRA Agile Scrum board for our team. Now I am wondering how to map my worklow states from to different workflows in my scrum board without adding a new column for each status.

1 answer

0 votes

Hello Natalie,

A JIRA Agile column can contain one or more workflow statuses associated. These statuses could come from different workflows as well.

This approach allows you to define macro statuses (JIRA Agile column) common to one or more statuses for a specific workflow or through different workflows.

Hope this helps,


That does not work. An issue has a workflow, that's it. It doesn't change between workflows. So, while you can define a new workflow and apply it to issue types, there's no logical link between the first workflow and the second.

issue-1 uses workflow-1 and issue-2 uses workflow-2. That's it.

I'm not sure I understand what you're looking for here. Sounds like you need to consider sub-tasks or having a workflow that includes your test steps properly.


I would like to ask one question related to the above. e.g. there is one workflow that relates to development team and for testing, we need to define new from one state of development workflow say "In Test" , can we map this state in another workflow designed for testing and based upon next transitions of testing workflow, it could update the state in development related workflow? Look forward to an urgent respone.

let me explain this further, e.g. development workflow starts from To Do, In Dev , In Test and Done. When any story / sub task is in test , I want to create another workflow that testing team follows. for testing team starting point is all those issues placed in "In Test" state and from that point they will start verification which either will be resolved as per the requirement or there will be a Bug in it. Testing team will create new bug and so forth continuing the workflow, once bug is fixed, that development item will be closed / reopened. Pl let me know if you need further detail.

That sounds like you need sub-tasks, and you have two approaches.

The first is that your bug follows to-do, in-dev, in-test, done. When a developer moves from in-dev to in-test, they should create one or more sub-tasks that represent the testing needing doing. The test sub-tasks can follow a totally different workflow. Then, when they are all complete, you can allow the top-level bug to be closed.

The other option is very similar, except that the top-level bug has a simple open/closed workflow, and the developers raise one or many sub-tasks alongside tests to cover their development work

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Confluence

Organizing your space just got easier - Page Tree Drag & Drop is here

Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...

101 views 3 4
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