nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot fill custom free text field on automated ticket creation

Benjamin Rosenek

Hello!

I am automating the creation of a couple of tickets that are required every quarter. For the most part I haven't had any trouble with this feature - I'm able to fill out the summary, description, and every required field, even some custom ones. However, there is one free text field in particular that just will not accept data from the automation process and I'm at my wit's end trying to find out why. I've even attempted a JSON solution and have had no luck.

This is the field, with the data I am trying to insert:

Here's an attempt to use the GUI to fill out the field as desired:

It returns an empty field when I run the automation in my test project:

Here's an attempt at JSON, which I am probably doing wrong. With this, I don't receive errors back but nothing happens, either:

Same thing happens - empty.

Anyone have any ideas? Thank you!

Accepted answers

Kian Stack Mumo Systems

@Benjamin Rosenek, what happens when you use the GUI? Just nothing happens?

All comments

Kian Stack Mumo Systems

@Benjamin Rosenek, what happens when you use the GUI? Just nothing happens?

Benjamin Rosenek

Yes, and I've edited the original post to be a bit clearer on that front. Ty.

Stefan Salzl

I guess where @Kian Stack Mumo Systems wants to lead with his question is „can you see the field when you CREATE an issue in the gui.

Fields depend on the screen scheme. If the field is not added to your „create“ screen the automation is not able to fetch the field either.

Could you share a screenshot of the audit log after a rule activation? In case it‘s a screen scheme issue this should give a hint.

Best
Stefan

Benjamin Rosenek

THAT WAS IT

The field in question wasn't in the create screen - I had no idea automation relied on screen setups, given that on the backend every field exists for every issue type. That explains a ton. TYSM!!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

custom-field

cloud

jira-software

jira-software-cloud

automation