how to configure secondary approvers in Jira, in case primary approver is on leave.
In some of our service requests we have an approvals required from different teams as well.
1 SR has been raised and fulfilment task have been assigned to
Desktop team approver in on leave, how to change approver from primary to secondary.
Hello @Waqar Mustafa
Delegating permissions has always been a missing point of Jira and there is no built-in solution to help.
My company has built Keychain app for this exact use case.
Keychain allows you to define delegates for any user in the system and you can authorize these delegates in your workflows (via conditions and post-functions introduced by the app); view them in issue view screens (via the custom field type introduced by the app); use them in permission, notification, and issue security schemes (via the custom field type introduced by the app).
Keychain even works on Jira Service Management Customer Portal approvals.
Finally, you can define Categories and delegate different permissions to different users.
You can find the details in our app documentation here:
Keychain works for Assignee delegation too.
First, let me say that all Keychain components determine the delegate users based on a given issueField/projectRole/userGroup. For example, delegate of the assignee, delegate of the reporter, delegate of the users in project role X, delegates of users in user group Y, and so on.
As for your question, there are multiple ways this can be implemented:
You can use the workflow post-function introduced by the app to assign issues to the delegate of a user in a given field. For example, you can configure the workflow transition to "assign the issue to the delegate of the current assignee".
Alternatively, you can use the workflow condition provided by Keychain and configure the workflow to allow a transition to be executed by the assignee or the delegate(s) of the assignee.
Finally, you create a Keychain custom field. This custom field can display the delegate(s) as defined above. For example the delegate of the assignee or any other (single or multi) user-picker field. You first bind the custom field to the assignee field. Then you add permissions to your workflows/schemes/etc based on this custom field.
When there are no delegates defined, these conditions/custom fields will have no value so will have no effect. When there are delegates defined for the assignee, they will use their names so will effectively authorize them in your workflows/schemes/etc.
It seems to be a little complex at first but Keychain provides the most comprehensive delegation solution.
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
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