Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Require 2 values for Affected Version(s)


When our testers creates a bug, I would like that they systematically indicate if this bug is present in the current and previous versions of our product. Something like "v20.2, v20.3" or "NOTv20.2, v20.3". i.e. entering "v20.3" is not good enough for me.

We are using the standard field "Affected Version(s)" and I would like to know if it is possible to enforce a control / post-function... that checks that the Affected Version(s) field has at least 2 values.

Thanks for your help.

1 answer

1 accepted


You can do it using "Automation for Jira" available for free in your instance. You can also do it with any of the third-party apps like ScriptRunner, Jira Misc Workflow Extensions, etc. 



Hi Radhika,

Thank you for the advice.

"Automation for Jira" does not seem to be available for Jira Cloud.

I tried "Jira Misc Workflow Extensions" but the workflow validators are only applied when users transition the status of an existing issue, not when they create an issue. This does not work for me as I want to make this validation when creating the issue.

I did not try ScriptRunner has this seem to require coding skills.

Any other suggestion ?


Hi Charles,

you can use JMWE to create a Validator that is applied during issue creation. Just add the Validator to the "Create Issue" transition (from the black dot to the initial status).

Thanks David, that works 
Have a great day :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Feedback & Announcements

The 2020 Content Awards

Happy New Year, Atlassian Community! In 2020 we all had to learn how to connect, share, and learn in an entirely different way. After a year of so much bad, we deserve to celebrate some good! The...

1,862 views 40 66
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you