Triggering a custom field from another custom field

[Susan Hamilton]

Hello there,

Appreciate your help!  

I have a custom field that is tied to my form where users select criticality from a dropdown (they can only select one option in the dropdown).  There are 4 different options.  I want to create a trigger so that if they select option 1 in that field that it auto-populates a specific value in another dropdown.  So option 1 in the original field would populate the "low criticality" option in the second field. 

I can't seem to put the rule together to do that.  

Any assistance is appreciated!

[yqiao · Accepted solution]

Hey I think maybe we can try following steps:

1. Go to Project Settings → Automation
(Or, if you’re a Jira admin, you can use global automation.)

2. Create a New Rule

• Click “Create rule” or “Add rule.”

3. Set the Trigger

• Choose the trigger “Field value changed.”

• Select your first custom field (the one where users pick the criticality).

4. Add a Condition

• Add a condition to check if the field equals “Option 1” (or whatever your first dropdown option is called).

5. Add an Action

• Choose the action “Edit issue fields.”

• Select your second custom dropdown field.

• Set its value to “low criticality” (or whatever value you want it to be).

6. Save and Turn On the Rule

[Trudy Claspill]

This would aligns with my question about whether or not the field needs to be updated in the form in real time or if the second field can be updated in the issue after it is created. 

If the field can be updated in the issue after the issue is created, then the above solution will meet the requirement.

If the field needs to be updated in the form as the form is being completed, then this solution will not satisfy the requirement.

[Trudy Claspill]

Hello @Susan Hamilton 

What type of project/space does this concern; Business, Software, or Service? The Forms functionality is different between Business/Software projects and Service projects.

Are you wanting to see the second field populated on the form in real time? Or would it be acceptable to have the second field populated in the connected Jira issue after it is created?

[Susan Hamilton]

Hi Trudy,

This is a company managed project/space. It's a JIRA space to manage technology tickets for managing our mortgage platform.  It's not a service space.

I think as long as once the issue is created the rule fires and subsequently populates the other fields that should be fine.

How complex is the other solution you were eluding too and what's the benefit to having it updated as the form is being completed?

Thanks!

[Trudy Claspill]

Hello @Susan Hamilton 

The forms functionality for a Software (non-Service) type of project space does not support specifying a default value for a field on a form.

It only allows you to conditionally (1) display a field (2) on the form based on the answer (3) for a previous field (4)

I think forms functionality in Service projects might support specifying a form field value based on the value in another form field.