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

How to block a transition, using a validator, if a field has a specific value without any plugins?

Danilo Simic

Hi everyone, I was wondering if it is possible and how to do this if possible.

In our Jira Cloud instance we have 4 Priority values which are "No Priority Set", "P3", "P2", and "P1".

I am wondering if it is possible to somehow block a transition (specifically the "Create issue" transition) if the value of Priority is "No Priority Set" without using plugins and using a validator.

I am aware that there is a Condition that can do this, but the "Create issue" transition does not have an option to add conditions. Maybe some workaround could be implemented?

Accepted answers

Ste Wright

Hi @Danilo Simic

Not that I know of using native functionality.

I'd recommend either...

Create an initial Status Issues go into, which can then have a Condition to get out of, requiring a P1-P3 Priority
Remove the No Priority Set Priority - and set the default Priority to P3, so it's detrimental to not change it to the correct one
Use Automation to manage for this - so if an Issue is created with No Priority Set, it could delete the Issue, or hide it (using an Issue Security Scheme), etc - and let a user know why this happened via Email

Let us know if one of these options works for you!

Ste

All comments

Ste Wright

Hi @Danilo Simic

Not that I know of using native functionality.

I'd recommend either...

Create an initial Status Issues go into, which can then have a Condition to get out of, requiring a P1-P3 Priority
Remove the No Priority Set Priority - and set the default Priority to P3, so it's detrimental to not change it to the correct one
Use Automation to manage for this - so if an Issue is created with No Priority Set, it could delete the Issue, or hide it (using an Issue Security Scheme), etc - and let a user know why this happened via Email

Let us know if one of these options works for you!

Ste

Danilo Simic

Thank you for the suggestions. This looks like a great workaround.

I will check if this works for the team.

Nic Brough -Adaptavist-

Yes, you can do this natively.

First, remove the "no priority set" option from the priority list. It does not make sense because it is a priority, so you are setting the priority, but saying you have not.

Second, in the project(s) that need it, make the priority mandatory.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

jira-cloud

workflow

validator

issue-create