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,460,928
Community Members
 
Community Events
176
Community Groups

Automate linking an asset when creating a service management ticket

Hello,

I am creating an automation rule to detect an asset that is "expiring" and creating a ticket for its renewal.

 

What is working:

  • having an automation rules that is scheduled
  • having a "for aql" rules that detect the matching asset ("expiry date" >= now() and "expiry date" < now(30d))
  • creating the ticket and being able to reference the object name

What is not working:

  • populating the "linked asset" field with the asset

Some context:

The "linked asset" is a custom field that allows to select an asset (type: Assets objects)

If I create the ticket manually I am able to fill the field.
But for some reason I am not able to fill the field in the automation.
The error is as follow:
"Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Linked assets (customfield_10066)"
After some search, the error is when the field is not available on the creation screen which is not the case here.
The json is as follow:
{
"fields": {
"customfield_10066": {
"key": "TCI-66"
}
}
}
Any help would be appreciated.

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events