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'm working on an automation for my team and im hitting a couple walls for it.
What i need:
When issue is transitioned to x and issue type is x, then create issue and copy x, y, z fields from current issue, AND link issue to trigger issue.
Most of the automation is working fine but 2 areas are failing:
One of the fields im asking it to copy is a short text field, and it's failing (although the other short text field is copying)
The action to link issue to the triggered issue is also failing entirely.
Can you please share the full rule that you have AND share the audit log that shows the errors?
A couple of things. It looks like you have more than one field called Facility - you should fix that so there are not duplicates there. Check the Custom Fields under Issues to see if there are two.
Second, I would add a branch after you do the Create. Make the branch for Most recently created issue.
Then move the Assign the issue to action and the Link Issue to action under the new branch.
Adding the branch worked! Thank you so much.
I'm still having trouble with the 'Facility' field, I double checked that we don't have duplicates of it and we don't. It's not a huge deal, since the trigger issue will be linked, but maybe I will reach out to Atlassian and see if there is something that I am missing.
Great! For the Facility field, you might have a Team-managed project that has that same field name. Are you narrowing down the rule to only one project? Or multiple projects?
That's very strange indeed then. You should definitely reach out to them. And please post back here with whatever the resolution was for future readers.