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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Create issue automation fails to populate custom field

Hi everyone,

I have created a manual trigger rule to create a linked issue on another project, taking some of the fields of the original issue.

I try to populate summary, priority, and 3 customer fields(Operator, Vendor, Regulation). It populates only 1 of the custom fields (Regulation). The populated one is Multiple choice, while those that fail are Label type.

Both projects have all 3 custom fields, both projects have permissions for the automation users. 

Action details:
Create issue
Issues created successfully
Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Vendor (customfield_11801), Operator (customfield_11802)
Link issues
Successfully linked issues
OP-1035, OPD-1775
Is there a limitation to populate a label custom fields or am I missing something else?


1 answer

2 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 17, 2021

The error message is telling you that the fields do not exist on the issue you are trying to update.

Either you're giving the automation the wrong fields to work with, or the fields do not exist for that project and issue type.  Try editing the issue to see if the fields are there.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events