How to make some fields (system and custom) required if system field got value?

Hi!

I have Components field.
and if Components value = Bug i need to make Description (system), Date (custom Date), Select list (Single) as required.

How i can do this? 

 

3 answers

Hi Sergey,

You can add a Simple Scripted Validator for each of those fields that checks whether the component has Bug as value or not.

You can find some examples of how to do that in the following snapshot of what will be the new documentation website, which will be released together with the next version of the add-on: https://scriptrunner.adaptavist.com/3.1.5-SNAPSHOT/jira/recipes/workflow/validators/simple-scripted-validators.html

Hi @Sergey Shcherbakov -

If you want to avoid code, you can use the Update on Transition for JIRA add-on from Bob Swift Atlassian Add-ons which comes with a validator named "Conditioned Validator."

With this, you would:

  1. Add a validator to the appropriate transition of your workflow, and choose "Conditioned validator"
  2. For Condition 1, type "%transition_components%:%transition_description%#%transition_MyDate%#%transition_MySingleSelect%#" into the first box (without the quotes), "Bug:.*##.*" into the second box (without the quotes), and select the Negative checkbox. This says to compare the concatenation of the Components field, description field, a custom datepicker field named MyDate and a custom Single Select List named MySingleSelect to a Regex expression that contains "Bug:" and nothing else (which it would be if any of those 3 fields were empty. The Condition1 must be true to "pass" the validation so we use the Negative checkbox to negate all this, in essence saying "as long as those concatenated fields don't match "Bug:" and nothing else, then all's good! wink
  3. The Message field provides the text the user sees if this validation is NOT passed.
  4. This screen print shows it all:
    uot-1.png
  5. Click Update, then you should see something like this (color coding used to separate the fields):
    uot-2.png
  6. Publish your draft workflow and you should be all set.

Please note:  The above assumes the Component, Description, MyDate, and MySingleSelect fields are all visible on the transition screen, which is why they are referenced with a prefix of "transition_".  If any are NOT on the transition screen, then replace the "transition_" prefix with "original_".

Hope this helps,
Betsy

 

Hi @Alejo Villarrubia [Adaptavist], I solved it is.
My code, for newbies:

! issue.components*.name.contains ('Bug') || issue.description as boolean
! issue.components*.name.contains ('Bug') || cfValues['Office'] as boolean
! issue.components*.name.contains ('Bug') || cfValues['Date of the bug detection'] as boolean

Thank you so much for cowork!

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Monday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

555 views 6 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you