Require one custom field to be filled out during transition based on another custom field

Jennifer Neusch November 6, 2024

Hi Atlassian Community,

You all were super helpful for my last question so here I am again!

I have a custom field where the options are Yes or Empty to indicate if the epic should show in some reporting. What I would like to do is require a different custom field called  "Release Date" to be required on a couple of transitions BUT only if this field has Yes checked. 

I thought I had done it correctly by choosing the Required field Validator first and adding an error message. And then going to Conditions but I think that's where I may have gone off track. What ended up happening is that issues could no longer transition to the next status. 

Thanks in advance for any help you can provide!

Jennie

2 answers

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 6, 2024

Hello @Jennifer Neusch 

The Required Field Validator (a native option in Workflows that can be used with Company Managed projects) will apply any time the transition is used. It does not inherently have any conditional options for it.

Is Empty an action value in your custom field, or do you mean the field can have no value (be empty) or be set to Yes?

 

What you could do is have two different transitions from the source status to the destination status.

  1. On copy A of the transition, use the Value Field condition to check that the custom field is set to Yes. On this same transition, add the Required Field Validator for the "Release Date" field.
  2. On copy B of the transition, use the Value Field condition to check that the custom field is not equal to Yes, and do not have the Required Field Validator in this transition. 

In the above scenario the transition that requires the Release Date field will be available only if your custom field is set to Yes. If the custom field is not set to Yes, then only the transition that does not require the Release Date field will be available.

Another factor to consider is if you otherwise have a Global Transition into the destination status. If you do, that is the one where you would want to apply #2. If you instead have only specific transitions from select other statuses to the destination status, each one would need to be set like #2.

Jennifer Neusch November 6, 2024

Hi Trudy! 

Thank you! I am going to try this out first thing tomorrow morning and will get back to you. 

Jennie

0 votes
Matt Doar _Adaptavist_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 6, 2024

The Required field validator is likely provided by an app, which should have docs about how to use it. Some validators allow you to add references to other fields, some don't.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events