Here is our situation:
We are moving a form into Jira SD to track employee information changes (i.e. job title change, work location change, supervisor change, etc.).As part of the migration we are adding approvals for submitted requests, approval is required by the new supervisor (if there is a supervisor change), HR, and a few others.The problem we are running into is a bit of a catch-22 with the optional new supervisor approval...
I can't figure out how to write the automation rule and configure the "new supervisor field" (optional/required) in order to allow for both: (1) the user from the field to be used as the "approver" and (2) the field to optional.
The issue is coming from the fact that JIRA seems to not let me auto-approve an approval when no "approver" is selected
The best solution we've thought of is really inelegant, namely:
Any recommendations for how to workaround this more cleanly than our current plan? Thanks!
Hello Community 👋, I'm a product manager at Atlassian, looking at improving change management capabilities across our products. In particular, we're looking at bridging the gap between Dev & ...
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