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; } } }

Get Value form Jira Form

Mergim Rexha

Hello,

I use the new tool used by Jira (forms). This allows you to quickly and easily create new forms so that they are then displayed in Jira Service Management for the end customer.

Previously, I worked with custom fields, which was more time-consuming.

My problem is the following: With custom fields, I was able to trigger the value being entered and display it in the title of a ticket, for example: {{issue.customfield_10084.value}}

For the forms, I am looking in vain for a field ID.

I read in a forum that this seems to work here (pro forma), but unfortunately the doc is not detailed enough. {{issue.properties. "proforma.forms.i1".state.answers.AAA.text}}

Here I wonder what is meant by "i1" and what is meant by "AAA". Or is this a plugin definition from Proforma and not from Jira Forms itself?

Would be great if someone here can give me information on how to trigger a form field.

Accepted answers

All comments

Jack Brickey

Hi @Mergim Rexha , as Forms is newly integrated solution I have not had much time to play/research. With that said I want to say that I seem to recall that Forms integration with automation is limited or absence. I may be wrong here for sure and I plan to find an official response on this. I (or someone) will post back here. I did find this old Thinktilt (developer of Proforma) cloud article that seems to qualify my belief.

https://docs.thinktilt.com/proforma/Jira-Automation-(Cloud).1571291510.html

Mergim Rexha

Thank you Jack.

I also read through the link and from there I also got the definition: {{issue.properties. "proforma.forms.i1".state.answers.AAA.text}}

He is also talking about an issue JSON in the settings, which I don't see or have at all.

Would be basically happy to find a solution here, because otherwise I would have to implement it with custom fields again.

Jack Brickey

I heard from colleagues that we should see the automation-forms support coming in the April timeframe. This could change but at least it is apparent it is active and near-term.

Mergim Rexha

Thank you for your feedback.
This means that there is no way to get the values by ID using Jira automation right now, correct?

Mergim Rexha

@Ste Wright

thank you for your feedback.
Unfortunately I have problems to understand the whole thing.
especially the topic with AAA.
What is AAA?
Is it for example the label? what I added in the form?
or do I have to assign a field key?

Could you please describe it in more detail as far as you can?

Shawn_Giese

Any update on "automation-forms support coming in the April timeframe"? Would be nice to use these values in automation.

Values like {{issue.properties."proforma.forms.i1".state.answers.AAA.text}} do not seem to be working.

Shawn_Giese

Got it, I was using a dropdown field in the Forms and the syntax to get the values was a little different.

Shawn_Giese

AAA is the id number of the field that you are trying to pull a value from (field on the form). Apparently when Forms was a plugin (before Atlassian integrated it to their product) there was a View JSON button to see this but I think you still see the JSON with something like:
https://<yourserver>.atlassian.net/rest/api/2/issue/<jira-ticket-number>/properties/proforma.forms.i1

I think Stephen got around the JSON view by testing with multiple calls first, one for each field on the form (in his case 15 different calls, each one with an incremented id # from 1 to 15) and figuring out the id number by matching the output.

We had dropdown form values to automate and that was even more complex since the form result is simply the position number of the choice... such as "3" to indicate the 3rd choice. We had to put that into a variable and pull the actual value shown in the 3rd position of the dropdown (with another smart field).

So, if you can identify that your form field id (AAA in the example) is "2" then you could get at it with a call something like:
{{issue.properties."proforma.forms.i1".state.answers.2.choices.get(0)}}

That is the the syntax for multiple choice in the forms. The link to proforma shows the syntax for other field types. Not robust though if tied to the location of the field. Debugging it is challenging.

Pieter Wouter Hartog

@Shawn_Giese What was the syntax you had to use for dropdown fields?

Mergim Rexha

Unfortunately, there is no update on this yet. You still can't trigger the data in a normal way from a form.

How I have solved this now, unfortunately, is that I have created custom fields, which I then link in the respective form in the respective field. This way I am able to trigger the content that the customer enters and use it in the automation.

Mergim Rexha

@Pieter Wouter Hartog

You need to create a custom field and then link it in the form on the right side, otherwise it is currently not possible....

Regarding your question:
Create a custom field, enter the data there, then jump back to the form and add a dropdown module and link it to your customfield. Then you just have to figure out what your custom field is. You can do that by creating a request type and adding your custom field there, then go into the customer's view, open the developer console and you will find something like this: customfield_100124
The syntax is then: {{issue.customfield_100124.value}}

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management