1 Project, 6 teams, each team have different workflow

[Mark Sayo]

I have one Jira project ​

And I also have multiple teams or 6 teams

Each team should have their own workflow and issue type ​maybe 1 or 2
What I want is if I created a ticket, it should assign it first to Team 1
Once Team 1 issue has been completed or DOne
It should create a new ticket to Team 2 with link to team 1 issue or ticket
Once Team 2 issue has been completed or DOne
it should create a new ticket to Team 3
this process will continue until it reach to Team 6

Is this the correct approach?

[John Funk]

Hi @Mark Sayo - Welcome to the Atlassian Community!

Posting this from my answer on the post Mohamed referred to:

One way to solve that is with a single project and workflow like you have it.

Then create a Group for each Squad and place the members in it. 

Then put Conditions on the Transitions to the phase that allows only that Group (Squad) to access it. 

Another way to do it with the same project and workflow is to create a custom field with multiple select. We call it Dev Needs. Then put the optional phases in the field. The user then selects the check box for the applicable phase. 

Then put conditions on your transitions again that check the Dev Needs field (or whatever you might call it) for that phase value. 

That is a quick solution although maybe not all that clean. It works for us though. 

[Mark Sayo]

Thanks @John Funk 
The reason that there is only 1 jira project is because each team is equivalent to the stages of SDLC.

I have different workflow for each team
Design, Build, Test, Deploy, etc...
And the documents are uploaded in Confluence

What is the recommended approach for example if the Design team completed their workflow?
I am planning to create a transition that when the workflow is done, it will automatically create a new issue to Build team and the link to Design ticket is link and also the confluence wiki.

[John Funk]

Yes, if each team has a different workflow, then you will need a different project for each team - each with it's own workflow. 

And you could set it up where the closing of one issue automatically creates an issue for the next team in the process. 

OR

You could still have a single Project with a single large workflow that allows the issue to flow from one end to the other.Then you could have different boards for each team with just the statuses in the workflow mapped to their board. 

The drawback to the one workflow option is that it makes it a lot harder to get metrics for each individual team. 

[Mohamed Benziane]

Hello @Mark Sayo 

Welcome to the community.

Take a look at this question here :

https://community.atlassian.com/t5/Jira-Software-questions/URGENT-Different-teams-Same-project-Different-workflows/qaq-p/1267466

You have two possibility in this thread, i prefer the one with multiple project, one by team, cause every team will have different needs in the future and it can be difficult to suit theirs needs