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

Can a Jira form set a value in a Jira field, without linking the form field to a Jira field?

Daniel Blomqvist

Hi Atlassian,

I want to use an internal Jira form to trigger certain actions using automation without adding a bunch of custom fields to the request type.

Current Scenario:

A request is submitted via the portal
A person reviews the ticket internally to prioritize and sets the priority field manually

When it comes to step 2 I want to use a Form to select radio buttons for Effort, Impact, and Deadline and based on the selected values automatically give the ticket a priority value from a drop-down list.

E.g. if Effort is High, Impact is High and Deadline is long set the CAP Matrix field to A2.

CAP Matrix Form.png

I know how I could do it if each Form field would be linked to a Jira field, but I don't want to add several Jira fields to each request type and was hoping to accomplish this using the selected values in the submitted form fields instead.

Can this be accomplished without linking the form fields to jira fields that are added to the request type?
If no, can I use jira fields without adding them (making them visible) on the request types issue view?

This example is for a quite short form but we want to use the same logic for forms that are longer.

I tried to create an automation using smart values based on the key set in the form field, but I'm not sure if this is the correct approach.

CAP Matrix rule.png

Accepted answers

Marc -Devoteam-

Hi @Daniel Blomqvist

That would be nice, and theoretically yes.

I do think it required to enable the save as PDF option, and you might need to do a re-fetch before the IF/ELSE

See if this makes a difference.

All comments

Marc -Devoteam-

Hi @Daniel Blomqvist

That would be nice, and theoretically yes.

I do think it required to enable the save as PDF option, and you might need to do a re-fetch before the IF/ELSE

See if this makes a difference.

John Funk

Hi Daniel,

I would say yes, if you used an automation rule to use those fields to do the action, based on a Form Submitted trigger. See this article for guidance on this new functionality for using Form fields in Automation rules.

https://community.atlassian.com/t5/Jira-articles/Forms-Automation-Access-form-fields-with-smart-values/ba-p/2862665

Daniel Blomqvist

Thanks @joh , the linked page Access smart values for forms and form fields in the announcement is what I have been using but I haven't been able to figure out which smart value to put in to an IF/ELSE condition to identify for example:

If the form field Effort is High set CAP Matrix to A1
If the form field Effort is Low set CAP Matrix to B1

I was trying to use {{form.last.cap_effort.High}} to identify High as the selected value in the Form field, but it doesn't seem to work.

Request Analysis Form.png

Daniel Blomqvist

Thanks @Marc -Devoteam-

The automation "technically works" it changes the CAP Matrix field when I submit the form, but it always stops/accepts at the first IF condition and sets it to A1 no matter what I select in the form.

I tried adding a re-fetch, but that didn't change anything.

Daniel Blomqvist

Sorry for the incorrect tag @joh I meant to tag @John Funk

Marc -Devoteam-

Hi @Daniel Blomqvist

I think you need to create 3 variables, based on the input of Effort, Impact and Deadline.

Then base the if/else options on the values stored in the variables and the options you can choose.

Daniel Blomqvist

@Marc -Devoteam-

To be honest, I haven't used variables in my rules before, so this is new to me.

I tried adding a variable for Effort to start with
Naming it CAPeffort
As the smart value, I used {{form.last.cap_effort.label}}
- As that should return the form field value High, Moderate, or Low according to this resource.
In the IF/ELSE I used the smart values condition and used {{CAPeffort}} as the first value and High as the second value
- Same but with Moderate and Low for the second value for the ELSE.

But the audit log says "The following issues did not match the condition:" for all of them.

John Funk

I just did something similar and used the {{smart values}} condition. The first value in your case would look like {{forms.last.Effort.label}}

Condition is: equals

Second value is High

Then put your action for Edit issue under that and set the CAP Matrix field to A1

Then put in another {{smart values}} condition for Low and set the field to B1

You might want to post your whole rule here though for help if that doesn't work as you would like.

Daniel Blomqvist

A possible workaround that works:

I tried linking the Effort form field to a (similar) Jira field called "Level of effort" (that I don't have on the issue screen or in the request type). level of effort.png

When the form "Request Analysis" is submitted
I used the "Level of effort" Jira field values as IF/ELSE conditions
To trigger an Action, in this scenario:
1. Hard (representing High) setting CAP Matrix to A1
2. Easy (representing Low) setting CAP Matrix to B1

This way I could accomplish what I wanted with the form without adding any custom Jira fields to the issue screen/request type, the values are logged in the background.

But it does require 1 custom Jira field per Form field, which I'm trying to avoid.

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