Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Custom field JSON Automation not populating field

Mark Jeavons
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 3, 2024

Using automation to fill my custom fields when creating tickets.

{
"fields": {
"customfield_14002": "User Induction/Laptop profile setup"
}
}

 This doesn't cause a failure the ticket is still created but the custom field doesn't populate. Use the same for other values which do work. I assume it is because of the forward slash, is there something I'm missing?

1 answer

0 votes
John Funk
Community Champion
June 3, 2024

Hi Mark  - Welcome to the Atlassian Community!

Is there a reason you are using JSON instead of just an Edit Issue action and selecting the field? 

Also, what type of field is it? 

Does the field have any restrictions based on Context? 

Mark Jeavons
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 3, 2024

Hi John,

I use the JSON as when this custom field is added as a field to populate in the automation I get the following:

Screenshot 2024-06-03 162430.png

This is a dropdown single selection field. It works with other options that are just words in automation but if it contains a forward slash it fails to populate and I need to update the field manually after the automation has created it.

 

John Funk
Community Champion
June 4, 2024

But why are you using JSON and not just using the field in the Edit Issue? 

John Funk
Community Champion
June 4, 2024

Screenshot 2024-06-04 121220.png

Suggest an answer

Log in or Sign up to answer