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,463,219
Community Members
 
Community Events
176
Community Groups

Automation on custom fields

Hi,

I am hoping someone can help. We receive a number of automated alerts through Jira and I am trying to set up an automation to fill certain fields however it will not pick up 2 of them so I am having to use JSON. I am using the below but the automation keeps failing. Can you please help?

{
   "set":{
      "customfield_11540":[
         {
            "value":"Support_Centre",
            "child":{
               "value":"IT"
            }
         }
      ]
   }
}

3 answers

1 accepted

3 votes
Answer accepted
Ismael Jimoh Community Leader Jan 02, 2023

Hi @Melissa Cross 

Looking at what you are aiming to do, I suspect you are trying to set the value of a cascading select field.

I will suggest looking at the following : https://community.atlassian.com/t5/Jira-Service-Management/How-do-I-set-a-Cascading-Field-using-Automation-in-Jira-Service/qaq-p/903653 though from just an initial look you seem almost there minus the square brackets.

 I t will also be Great to see the exact error you are getting from the automation log.

@Ismael Jimoh I now have a functioning automation! Thank you

0 votes

@Melissa Cross -

Hi Melissa:

Two things that you may also want to check (in addition to what @Ismael Jimoh suggested) -

1) For the custom field (cascade select data type) - Are the values that you try to populate the issue are defined already (exact spelling) in the field configuration dropdown?

2) Is the custom field (in question) exposed to your JSM project in question? Example - Field itself is setup with proper context configuration against your JSM project and issue types?  Field has been added to the JSM project's issue screens to the appropriate issue types?

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Hi @Ismael Jimoh 

Thank you for your response, I will take a look at that. Yeah, I feel like I am so close.

This is the error:

Edit issue
No fields or field values to edit for issues (could be due to some field values not existing in a given project):
Ismael Jimoh Community Leader Jan 02, 2023

Looking at the error you shared, I will also verify that for this field, in the field mappings for the project the automation is running in, the value is available.

I will first of all try what was suggested in the linked ticket (it contains a link to Advanced automation configurations and from here, you can see how to set the value for a cascading select list).

Let me know if this solves the issue for you.

Suggest an answer

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

Atlassian Community Events