Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×background...
often we have specific issues that require an extra layer of approval before the issue (story, bug etc.) is release from staging to production. how can we add this to jira?
once solution/approach...
a way for the issue creator to tag it as "requires additional approval"
going forward any issue tagged as such will not be released by the dev team (from staging to production) unless flagged as approved.
how can we accomplish this? if you have similar scenarios kindly share your implementation.
thank you.
Hi @raffi
You could do this by adding an approve transition before release for the issue and then have the approver set in a user picker custom field.
Add a condition to the approval transition restricting the transition to the person in the custom field.
Jira Service Desk has an approval process built in that can be enabled in the workflow that does the above more efficiently.
Yes it works for JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"then have the approver set in a user picker custom field."
where can this be done, please?
same Q re the following...
"Add a condition to the approval transition restricting the transition to the person in the custom field."
furthermore, the new transition should be conditional on a new checkbox being checked either when the issue is being created or edited!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.