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

Specific issue type ticket cannot move to done or dev complete if a custom field is not filled in.

Deb Keene

We have multiple issue types in a project and all the issue types share the same workflow. I want only task and bug issue types to have to follow a rule that a custom field must be filled in before the task or bug can move to dev complete or done.

Is it easier to create a separate workflow for the task and bug so if I set up a condition/trigger I only impact those issue types?

Or would it be easier to set up an automation rule? If an automation rule- would appreciate some guidance. If I triggered on issue transitioned- the "from status" could be almost anything so not sure what to use as a trigger

Accepted answers

John Funk

Hi Deb,

It is best to just add another transition to the two statuses. Then you would need to add Conditions for each of the transitions going to those statuses to check the value of the Issue type. This leaves you with one Workflow to maintain instead of two.

All comments

Vishal Biyani_2pr07j

@Deb Keene

in my opinion, it will be better to create a separate workflow for Task and Bug so that you can put a validator condition before the issue is transitioned for the specific issue types.

Transitioning an issue back to previous state is complicated using automation rules

John Funk

Hi Deb,

Maciej Dudziak _Forgappify_

Hi @Deb Keene

There is a third option: you can use Jira expression-based validators, which allow you to require a field conditionally. However, this is only an option if you are open to using apps.

Cheers

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud