You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a parent ticket with first level of approval (called Department Head Approval).
Department Head can be anyone whichever user picks on the request form while submitting.
When Parent ticket is created and it is transitioned from "Awaiting Department Head" to "Department Head" approved , a child ticket will be created and we will have the 2nd (Audit approval) and 3rd (CIO approval) in the child ticket.
In the 2nd and 3rd approvals , we are directly passing the value of specific user as "Approvers".
If the Department Head on the parent ticket approves it and if the same user in the Department Head matches with the Approvers in 2nd or 3rd approval on the child ticket , we need to auto-approve that approval in the child ticket and move further to the next approval process.
May I know how can we achieve this ?
Hi @Manoj Kumar Emmadi , thank you for your detailed explanations.
As I understand it, you need another, hidden transition on the subtasks that cannot be triggered by a user. If such a subtask is created, an automation should now check whether the person in the parent's approver field and here in the subtask created are identical. If this is the case, the transition is used for bypassing.
The point is, however, that I don't know exactly whether comparing two fields in the automation is available on the server. If not, use scriptrunner.
This is how I'd write the automation in cloud. In this example I am comparing the parent approver with the subtask reporter as I don't have approver in my subtasks.
Hi @David Friedrich ,
Thank you for the valuable information.
I have tried another approach to auto-approve if the approver in the parent ticket gets repeated in the child ticket using "Legacy Automation" in that Jira project.
I have created a custom field in parent ticket to copy the value of approver to that field and compared it with the approvers in the child ticket and then set it to trigger the above legacy automation rule to auto-approve (using JQL condition if approvers match).
This helped me to resolve this issue.