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 deny transition if a field in the issue is empty?

unknown

Hi, I would like to setup a rule or condition in the workflow that deny transition to the next status in the workflow if a specific field is empty.

When a developer want to start working on a issue (from Selected for development to In progress) and one specific field are not filled in, I want to block that transition.

My guess is that this would be something to add in the workflow, been looking into conditions but cant find how to do it?

Accepted answers

All comments

Paula Kraszewska

Hi there,

You can add a Validator to this specific transition. There's Field Required Validator available that checks if the field is not empty and if it is empty, doesn't allow to transition. Most of the time when we use it, we create transition screen to allow users to fill it in while transitioning.

Trudy P Claspill

Using a Validator will allow the user to click the button to attempt the transition, and then not let the transition happen. If you want the user to have the option to fill in the field as part of the transition process, you can create a screen that includes that field and attach the screen to the transition.

If you don't want the transition to be available to even select when that field is empty, you can use a Condition. The specific Condition you would use would be the Value Field condition. This condition does not work for all field types, though.

Screen Shot 2021-11-10 at 5.25.44 PM.png

Manoj_4r4x3x

@Trudy P Claspill Hello,

I have a custom field value, if the amount is =>200k then it will assign to finance head for approval and if it less then simply move to approved stage, How would I achive this, can you guide me on this.

Trudy P Claspill

@Manoj

Please start a new post/thread for your question.

Andreas Borkenhagen

Any chance to achieve this in Jira Software Server (without any payed plugins)?

Trudy P Claspill

I don't have access to a Jira Server environment without any third party apps where I can investigate this.

I found these articles from Atlassian about the having a Required Field validators natively:

https://confluence.atlassian.com/adminjiraserver/using-validators-with-custom-fields-938847524.html

https://confluence.atlassian.com/jirakb/make-custom-fields-required-in-a-workflow-transition-in-jira-server-691011903.html

https://jira.atlassian.com/browse/JRASERVER-5783

https://jira.atlassian.com/browse/JRASERVER-9088

Andreas Borkenhagen

Thx for trying to help, but:

1st one is "Jira Suite Utilities" (our proxy blocks access to that page)
2nd one is "is not available in Jira out-of-the-box." (paid plugin)
3rd one is "Jira Suite Utilities" again
4th one is "Won't" fix with 2 dead links within

Trudy P Claspill

I provided those links as documentation that Atlassian doesn't intend to provide the functionality (i.e. status on Jira items is Won't fix) because, as they note, it is available through third party apps.

I am not aware of any method to achieve what you want on Jira server without a third party app.

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-software-cloud

transition

workflow