Different workflows for different boards within the same project

[Gary]

Hi All,

Looking for a bit of help regarding potential ways to manage a project.

I have a project where tasks require to be triaged, then depending on the outcome of the triage the task would then be flowed down to other department boards. Please see attachment of this flow.

Ideally, this would all be held within the same project with the triage board being at the top and the tasks subsequently flowing down to the different boards. However the triage board would require a different workflow compared with the other boards. Is this possible? 

The other option would be to have the triage board as a separate project and then depending the outcome the tasks being flowed into a different project board. Is this also possible?

All help appreciated.

Cheers,

Gary

[Ramakrishna _RK_ · Accepted solution]

Hi @Gary ,

Welcome to the Atlassian Community!

Below is the solutions proposed to achieve in a single project. Please review and if answer your question, accept the solution.

• In the given project, create an Issue type 'Triage' and associate it with workflow required , and have issue type 'Task' and mapped to different workflow.
• Create a board based on filter pulling Triage Issue types, which is Triage board.
• Based on triage, you can manually or using Automation you can create tasks in different boards which are configured based on some differentiating factor for example custom field Department.

Please let me know if you have any questions.

Regards

RK

[Gary]

That's great thanks for your help!

[Radek Dostál · Accepted solution]

I think what you need to look at it as is that you specify workflow on an issue type basis, for each project. So the only way you can have 2 different worklows is if you use 2 different issue types.

Alternative to that would be 2 different workflows with 1 issue type, but then you need 2 projects.

As for boards, it doesn't matter if you have 500 of them. If all of them show that issuetype from that project, all 500 of them will work the same with it, because boards are just visualization and nothing more.

The only thing about boards here would be clarity - is it good to have all of this on just one board, or should each department have their own board? If you go with one, you might get into filtering hell and departments may get confused what is for them and what is not, or at which stage they're supposed to be interested in something, etc. A single board for a department might make it pretty easy in comparison.

[Gary]

Thanks a lot for your help, this gives me a greater understanding of it all