🎉 New! Access form and form fields with smart values in Jira Service Management

[Tejas Patil]

Hi @Hanh Pho,
Got it, That's helpful as well.

Thanks.

[David Foote]

@Kelby Corr 

Not sure why you'd get different results. 

I'm not crazy about loading the forms page, using the developer tools, going to the Network tab, then finding 'forms' and then selecting 'Preview'. Especially when you have a huge number of forms, I think it would be easy to get the wrong form.

For me, on a test project where I had just one form, it was pretty easy to line them up and I got the same UUID via both methods:

If you have multiple forms attached to a card, you might need to use list operators to get all the ids.

[Bao Truong]

@Sam Knight You should also mention that the old method of using Jira entity properties will be removed, so people can plan to replace it. 

https://community.developer.atlassian.com/t/removing-access-to-forms-data-using-jira-entity-properties-api/80912

Also, this new way takes more time to run than the old way.

[ヴァリエンテ フロリアン_Florian Valiente_]

Trying this out now, and the smart values doesn't seem to work with fields that are using a data connection? The returned value and id for the dropdown are always blank. Same smart value on a static dropdown works.

EDIT: 2025 March 07 - created a support ticket and have confirmed it now works for fields using data connection too!

[Phong Nguyen - Atlassian Solutions Engineer]

@Sam Knight @Hanh Pho Could you please provide more clarification about this related post? https://community.developer.atlassian.com/t/removing-access-to-forms-data-using-jira-entity-properties-api/80912

We’ll soon be removing access to Forms (previously ProForma) data currently stored in entity properties from both Issue properties routes and Project properties routes.

Do we have a plan for when we will remove it? It's crucial that we prepare in advance to transition to the new methods for accessing the form data. Thank you.

[Phong Nguyen - Atlassian Solutions Engineer]

*Deleted*

[Mauricio Heberle]

Anyone else having trouble when trying to retrieve single user fields?

[Thong_Tong]

Accessing form field data is very useful for us. I tested this out, and the Forms Submitted trigger worked great. However, sometimes I need to use a different trigger while still accessing the form fields. So, I tested the {{issue.forms.<UUID>}} method, but when I tried to access a checkbox form field, the returned value looks like:

[value1, value2, value3]

For some reason, the brackets are automatically added. They aren't there when accessing the same field via the Forms Submitted trigger. Has anyone encountered this before, and how did you handle it?

Thank you!

[David Foote]

@Thong_Tong I've seen this is other places, where I expect the smart value to come back as a list, but it instead returns a string, with the brackets.

If you just want the values without the bracket, it's pretty easy to just use replace to clean it up:

{{teamsText.replace("[","").replace("]","")}}

If you need it as a proper list, for example to use in an advanced branch, you can use split on the results from the above:

{{teamsList.split(",").distinct.trim()}}

[Thong_Tong]

Thank you for your suggestions, @David Foote .  I found my answer in Solved: Form dropdown field smart value post.  Short answer to remove the brackets, use the flatten() function like

{{issue.forms.<UUID>.<Field key>.label.flatten()}}

[Tobias H]

Hi all!

Just throwing this in here as I had not seen any communication about it.
You no longer have to fiddle about with the Inspector tool and search the network tab for the ID, you can simply press the three dots and "Copy form ID" to swiftly get the ID for any of your automation needs :D