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
In Jira Cloud, I have an automation that creates an issue in a classic business project when a certain label is applied to an issue in a next-gen project. As part of the new issue creation, in the "choose fields to set", I selected Linked Issues and selected a new custom Link Type, "Initiated By".
The automation successfully creates the new issue but is unable to create the link, erroring with the following message,
"Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Linked Issues (issuelinks)"
I also tried it with the "Relates To" link type, with the same result.
I can open the issue in the next-gen project and can create a link, using the custom link type, without any problem, it just does not appear to be possible using the automation.
I've passed this error onto the team to look at.
In the meantime you could link the issues in a separate action. I would set the scope in the rule details to the projects you're linking between.
Your rule might look something like this:
Hi Ryan - I know that Next-gen (Team Based) projects don't use the normal Epic Link field to linking Epics to Issues. So I thinking the same is probably true for linked issues.
Maybe someone from the Atlassian Automation team can verify and provide new syntax.