Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,228
Community Members
 
Community Events
176
Community Groups

Is there a way to create a link to an issue in a next-gen project using Jira Automation?

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.

2 answers

1 vote
John Atlassian Team Mar 31, 2021

Hi @Ryan McBryde 

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.

Screen Shot 2021-04-01 at 12.22.11 pm.png

Your rule might look something like this:

Screen Shot 2021-04-01 at 12.20.15 pm.png

Thanks,

John

0 votes
John Funk Community Leader Mar 31, 2021

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. 

Thank you John,

Is including the "automation" tag sufficient to get them to address this question or is there a better way?

John Funk Community Leader Mar 31, 2021

It probably wouldn't hurt to go ahead and open a support ticket with Atlassian. Then please post back here what the resolution ended up being. 

https://support.atlassian.com/contact/#/

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events