Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,254,203
Community Members
 
Community Events
164
Community Groups

Require 2 values for Affected Version(s)

Hi,

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

Hi,

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. 

Regards,

Radhika

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 ?

Thanks

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
TAGS
Community showcase
Published in Atlassian Account

How to change your Atlassian account email address

When using an Atlassian account that is not managed, it’s possible to change the email address, but we often receive the following notification on the email that we want to use: Sorry, we couldn'...

729 views 3 14
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