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; } } }

Workflow condition based on reporter

Frank Koehl

Our workflow process has a forking event based on the group who creates the ticket. If our dev team opens an issue, it goes through a Dev QA process. Alternatively, if our client team opens a ticket, we send it back to them for QA and approval.

I only ever need to present one of these two QA transitions, based upon the original reporter. However the available conditions logic does not appear to support this notion.

Can anyone confirm, or provide an alternative? Using Jira Cloud.

Accepted answers

Petter Gonçalves

Hello Frank,

I think that the best option for you in the scenario you mentioned is to use (Or create) two different issue types:

Dev Task - When created by the Devs.

Client Task - When created by the Clients.

Performing the steps above, you will be able to configure two different workflows for the Issue types and decide what steps you want to configure.

Please, let me know if it makes sense for you.

All comments

Petter Gonçalves

Hello Frank,

I think that the best option for you in the scenario you mentioned is to use (Or create) two different issue types:

Dev Task - When created by the Devs.

Client Task - When created by the Clients.

Performing the steps above, you will be able to configure two different workflows for the Issue types and decide what steps you want to configure.

Please, let me know if it makes sense for you.

Frank Koehl

It was overkill to create two workflows for a single forking step, but I did end up using two different issue types.

At the fork, I added Value field conditions on each QA transition to look at the Issue Type. The condition ultimately looks like this:

The field Issue Type will have to be equal to value 'Dev Task'. Compared as String.

Hope that helps a future traveler, and thanks @Petter Gonçalvesfor pointing me in the right direction.

Petter Gonçalves

You are welcome, Frank.

The condition you used was a good idea as well.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

transition

workflow