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
Next: Root
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
Hi,
I have scriptrunner job / Escalation service where is Action (= status change) and assignee change by "Additional issue actions".
Both actions works ok separately, but when I add both actions in same Escalation service user is almost assigned - meaning assignee change is mentioned in Activity All list, but Assignee is not changed.
Proposals what is problem/should be done. Temporary workaround is to do change in 2 steps with separate jobs (first change assignee and then status).
First, have you confirmed that your status change is not causing the assignee to change via a post function? If so, any way to make that conditional?
yes that's for sure as it works with 2 separate jobs and those jobs run order did not change functionality.
Changed functionality in the way that transition is triggered as job and assignee change is handled in conditional post function and now one job is enough.
It is great to have multiple ways to do things - it gives possibility for workarounds which are not bad at all.
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.