Two stage approval for Change Request, prevent same group being added to the second stage.

[Nick Shehan _Emergency Admin_]

In our workflow we have peer approval for a change request ahead of it going to CAB.

At the peer level we select a relevant group related to the assignee. Once this has been approved the next stage is to go to CAB for approval but this is automatically being populated with the same group that was used for the first approval.

How can I prevent that?  I've tried using services to select the approval group, this works but also keeps the first approval group from the peer stage.

Thanks

Nick.

[Pablo Vergara · Accepted solution]

Hi Nick (@Nick Shehan _Emergency Admin_

I've been looking for an option you can try and come out with the following strategy:

• Use an Automation for Jira rule to set the "Approver groups" field
  • The idea here would be to set the "Approver groups" field each time: 
    • Issue transitioned from X to Y (approval 1 stage)
      • Set the "Approver groups" field to a specific value
    • Issue transition from Y to Z (approval 2 stage)
      • Set the "Approver groups" field to another value
• Hide the "Approver groups" field from the creation and edition screens so it cannot be modified.

I haven't tried it, but I'm confident it should work.

Give it a try, and let me know how it goes ;)

- Pablo / SSE - ServiceRocket

[Nick Shehan _Emergency Admin_]

Hi Pablo,

Thank you, that was very helpful. I changed that slightly but otherwise that was exactly what I needed to add the relevant groups.

Cheers,

Nick.