nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

A issue following 2 workflows?

Quinn Campbell

I have a form create an issue that follows a set workflow through 6 standard workflow progress points (call this workflow A). As that issue goes through those workflow(A) points new subtasks are assigned to different team members.

Currently the issue only is moved when all subtasks for that workflow status are complete.

I have a second workflow(B) that needs to be triggered by moving the issue into one of the set progress points on workflow(A). That workflow(B) that would be run by a different team that would have its own workflow progress points that related directly to the issue. What is the best way to have an issue mirror/visible/seen between workflows with different tasks that need to happen simultaneously (without each team needlessly seeing all the subtasks from the other team)?

Accepted answers

Tim Kopperud

Hi @Quinn Campbell, just to be sure I understand your question propperly.

On worflow B, you do mean another issue in the other team, so in your scenario you have two issues (not including subtasks)?
Based on one of your other questions, I understand you are using Cloud. I suspect this question also involve a cloud instans, is that correct?

Rationale for the questions:

1: An issue cannot span two worflows, so just to confirm we are on the same line here.

2: Some admins, like myself, swap between cloud and server/dc several times per week hence the questions posted by a single user might impact different hosting types. And an Automation rule example will differ based on the hosting type.

TimK

All comments

Tim Kopperud

Hi @Quinn Campbell, just to be sure I understand your question propperly.

On worflow B, you do mean another issue in the other team, so in your scenario you have two issues (not including subtasks)?
Based on one of your other questions, I understand you are using Cloud. I suspect this question also involve a cloud instans, is that correct?

Rationale for the questions:

1: An issue cannot span two worflows, so just to confirm we are on the same line here.

TimK

Quinn Campbell

@Tim Kopperud thanks for the response. We are using Jira Cloud (Software & Work Managements) and that is the only version we have access to (I believe, new to this software in general).

1. 2 separate issues could be a solution. If it were 2 issues, would it be possible to have 1 form trigger an issue on 2 different boards/projects? My basic request is to have mirrored initial data between issues on 2 boards run by 2 different teams but triggered by team A's form. Writing this out a solution could be to have when an issue is created on board A create an issue on Board B, if that is the solution then what is the best way to copy all the initial form data to the new issue created on board B?

2. Cloud as mentioned

Tim Kopperud

Hi @Quinn Campbell, if I understand your requirements correctly you can use one single workflow, one single issue type, one single project and still divide into two (or more) boards for the two teams. This is a common way of solving handover from e.g., Team A to Team B.

So, for Team A. the end column (right most) in their board will be the first column (left most) for Team B.

You will need to design a single worklow spanning tasks for both teams. Then you need to map the statuses relevant for Team A into their "Board A", and for Team B into "Board B".

The table below shows a simplified example of this principle (issue progresses from top to bottom).

Team	Status	StatusCategory	Board
A	New	To do	A -> To Do column
A	Development		A
A	Test	In Progress	A
A and B	Ready for release	To Do	A -> Done column B -> To Do column
B	Plan release	In Progress	B
B	Release	In Progress	B
B	Done	Done	B -> Done Column

Please inform me if I misunderstood something, and this is not the correct approach to solve your requirements.

Notice:

In JSW a board is not limited to a single project. The board content is based on a JQL filter which can include several projects and several issue types.
A workflow is one-to-one with an issue type within a project. You reuse a workflow though,

TimK

Quinn Campbell

So what I figured out worked best for us was to have when 1 board created an issue trigger a clone issue on team B with the relevant data copied over. Then work flow B happens simultaneously with different tasks on another board. Thanks for the help.