Unique workflows and boards for two teams within one project

[Mikael Underwood]

Hi all!

I have a project where I have one development team, where changes and new features are developed and deployed to existing markets, and one rollout team that is focusing on deploying the solution to new markets. 

I would like to have them in one project, as the two teams work closely together on the solution, but I want them to have different workflows and boards as they also work independently of each other.

As I see it, the workflow setup should not be an issue, as I can have different statues for the development and for the rollout process, so statuses do not need to be shared.

My question is, how exactly do I create the two workflows, and then have them displayed in separate boards? I am not clear on how do create one workflow, add it to board, ad then create a second workflow, and add it to a second board. Do I first need to add all the statuses used by the two teams into the project, and then somehow create the two workflows from them?

Are there clear instructions on how to achieve this? 

Kind regards,

Mikael

[Dave Mathijs]

Hello @Mikael Underwood welcome to the Atlassian Community!

You can only create 2 separate workflows if you have (at least) 2 separate issue types.

A Workflow Scheme consists of one or more workflows:

• You can either have a single workflow for all issue types OR
• a separate workflow for each issue type (or a group of issue types) which is best practice

What you cannot do is use the same issue type with 2 separate workflows (because you have 2 separate teams).

The only option would be to create additional issue types, but that would be a bit weird because a task is a task, a story is a story and an epic is an epic.

So, rather than customizing the tool to fit the process, why don't you standardize the process for both teams? Why should one team use a (completely) different workflow than another team? I don't see the business case for that.

[Mikael Underwood]

Thank you @Dave Mathijs for your answer! Streamlining the process has not quite worked for the two teams before, but it is something we could definitely revisit. One issue there is that the teams have some very different statuses to track their work which make streamlining their process difficult. Perhaps using sub-statuses could work to get them on the same page, but that would still leave gaps in the process that don´t quite fit.

But if that is not possible, is it possible to use user stories for the dev team, and "rollout user stories/tasks" for example for the rollout team? I m thinking that as the rollouts is more of a waterfall process, where the team goes through different steps towards the rollout, could that workflow use a different naming setup?

Or, is it possible to edit the status column names in one of the boards, so that while not a different workflow, that team can have their own statuses on board?