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,464,724
Community Members
 
Community Events
176
Community Groups

Automation for Jira throwing "Unknown fields" exception in Create Issue action

Edited

In an automation rule I am using the Create Issue action to create a subtask. Within the action I am attempting to set the LinkedIssue field to an existing issue. Although the LinkedIssue field is enabled for the subtask issue type in my project, the link is not being created. The audit log shows the following error:

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Linked Issues (issuelinks)

 I have tried adding the link both directly by choosing a field to set, and with JSON in Additional Fields. Both ways return the same error.

Does anyone know why I'm getting this error even though the Linked Issues field is enabled for this issue type in my project?

1 answer

1 accepted

Found the solution in another community post: Automation for JIRA - Linking issues.

For others, the Linked Issues field (or any field used in automation actions) needs to be on the associated screen (e.g. create or edit). Adding the field to the create screen resolved this issue.

Just speculating, but it sounds like issue screens are used for validation, etc. in the rule actions. Wouldn't be surprised if the same is true for imports.

I was having exactly the same issue, and adding the linked issue field to the create screen solved it.

Too bad, I can't "hide" this linked field on this issue creation step. It really doesn't make any sense to have it in my application, at this point.

Like Steve Goodwin likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events