I have a custom field called Estimated Price, which has three options.
1. [0-5000 USD]
2. [5000-50000 USD]
3. [>50000 USD]
What I want is the following Approvers field to be populated with a certain user depending on what option you choose for the Estimated Price custom field.
Is this something that's doable with a script-listener?
Best regards,
Jesper
Hi @Jesper Fransson - I see you're on Jira Cloud. You can accomplish this with native Jira Automation:
Estimated Price
Equals
"[0-5000 USD]"
Estimated Price
Equals
" [5000-50000 USD]"
Estimated Price
Equals
"[>50000 USD]"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can change the trigger in my example to Issue Created to have it execute when the form is submitted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't have it trigger in real time on the issue event of a custom field changing value?
Like a listener.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not natively, and I don't believe scriptrunner listeners work in Jira Cloud if this is the desired end goal. What is the use case for having it trigger immediately while the form is still in progress? Is the expectation that these fields get pre-populated with a default value, but the user has the ability to override? If that's the case, I'm not sure this is possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'll have to take that up with the scriptrunner support I reckon.
The use case is that you shouldn't be able to remove or forget the user who needs to approve the issue, but you should be able to add more approvers in addition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In that case, you could allow the user to select whatever approvers and then append that list with the desired defaults via automation after the issue has been created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That list would be too long, hundreds of possibilities. But thanks for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Will this trigger when you're filling out the form?
That's the end goal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Earning the Mindful Member badge proves you know how to lead with kindness, plus it enters you into a giveaway for exclusive Atlassian swag. Take the quiz, grab the badge, and comment on our announcement article to spread the good vibes!
Start here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.