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

Help with Automation to set a field value based on certain criteria

Juliette Bramall_adkwzy

Hello fellow Atlassian-ers

We have a custom field called 'Closing Category', a field called 'Test Phase' and a third field called 'Root Cause' for a bug issue type.

I've been asked to automate the 'Closing Category' which requires a conditional update based on "Root Cause" field as below,

If (Test Phase is " User Acceptance Testing" or "Production") and Status is "Closed" then

{

if (Root Cause = "Cutover") then Closing Category = "Production Deployment / Cutover Issue"

if (Root Cause = "Duplicate" then Closing Category = "Invalid"

if (Root Cause = "Existing Production") then Closing Category = "Existing Production issue"

if (Root Cause = "Invalid Defect") then Closing Category = "Invalid"

if (Root Cause = "Non Reproducible") then Closing Category = "Cannot be tested, no clear recreation, speculative fix"

if (Root Cause = "Requirements/Specification") then Closing Category = "Requirements change raised in pilot or rollout"}

Can anyone else me set up the automation, including triggers and components, etc. I'm a bit of an automation novice when it's anything beyond the basic

Thanks in advance!

Accepted answers

All comments

Vishal Biyani_2pr07j

@Juliette Bramall

Please share more context for community to help you.

How are the values populated in Custom field "Root Cause" and "Test Phase"? is it on a status Transition of the issue or is updated manually?
Is the automation rule applicable for a specific issue type?

Juliette Bramall_adkwzy

Hello @Vishal Biyani

Yes, it's on transition from the status Retest to the Closed status.
It's for bug issue types

Vishal Biyani_2pr07j

@Juliette Bramall

Please implement these steps and share your automation rule screen shot if you face hurdle.

1. Trigger

Add Issue Transitioned trigger

In from status add Retest (Should exactly match your status name)
In To status add Closed

2. Click on Add Action and search for Add If condition

if issue type equals Bug

3. Add Lookup Table

Click on Add an Action and search for lookup table

Provide lookup table variable name say ClosingCategory
specify your conditions for root cause e..g key = Cutover value = Production Deployment / Cutover Issue

4. Click on Add Action and search for Add if block

In Conditions add

Field = Test Phase

Equals User Acceptance Testing

Field = Test Phase

Equals Production

5. Click on Add Action and search for Create Variable

Name the variable say RootCause and in smart value put

5. Click on Add Action and search for Edit issue

In Choose field select Closing Category

and in the text box below put {{ RootCause }}

Let me know if this works for you.

When the transition happens, then you should see Closing Category updated.

Juliette Bramall_adkwzy

Step 2. Add If condition didn't appear when searched for?

Juliette Bramall_adkwzy

sorry, I Screenshot 2025-02-10 120929.png thought I had. Here it is

Bogna Krystian_Deviniti_

@Juliette Bramall

Hey Juliette, you can set up a rule that is triggered when an issue transitions to the "Closed" status. The rule would check if the Test Phase is "User Acceptance Testing" or "Production" and if the Root Cause is "Cutover", then update the Closing Category accordingly.

Alternatively, if you're looking for a way to handle this directly within the issue form, some Jira add-ons (for example, Dynamic Forms) allow you to configure conditional behaviors. This means the Closing Category field could update in real time based on the value selections in the Test Phase and Root Cause fields while the user is filling out the transition screen- without needing a separate automation rule. This could simplify the setup

Juliette Bramall_adkwzy

Hey @Bogna Krystian_Deviniti_

Thanks for pointing me in the direction of the add-on. Much appreciated.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-automation