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
We're attempting to automate a status transition of a particular issue type when an update is sent via Salesforce. The actual transition does appear to work but we're getting an error in the log.
Rule and error attached.
My suspicion is that the error is occurring due to the number of times the issue has entered this state (Reopened - 4) and it's actually a bug with the report. But am I missing something?
Note: the issue does actually successfully transition to Reopened.
We are using Jira Cloud.
Kind regards and many thanks for any feedback.
Thanks for your feedback Danyal.
Forgive me but I'm not familiar with the concept of a "global" transition?
Is it simply the case that any status is permitted to transition to it?
If so, then i'm not sure why it would only be a log error and not actually fail completely.
agree. and the fact that the transition did actually occur tells me that either the automation worked or the issue was already in the status associated w/ reopened transition. I might consider improving your conditions a bit to align w/ your workflow. If you have an "All" transition into the status that is associated with reopening then it is pretty easy - just add a field condition to check that you are not already in your target open status. if you are not using an "all" transition then you need to consider the from statuses that you could be in when this rule triggers.
As stated it appears that the transition is working correct? If so then I think it is just a false error which I have seen before when the automation doesn’t run cleanly. With that said I would recommend you do a couple of controlled tests on this just to try to understand the error. It would be interesting to use the log event action to capture of the incoming status.