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

How can I use automation to assign a custom field called "PAIR "

Glenn_Riley1

How can I use automation to assign a custom field called "PAIR " which is the QE tester to the QE s

The status is getting changed to Defined

The Assignee of the subtask remains unassigned

What changes are needed to get the assignee to match the PAIR field from the Parent?

Move Subtask to Define status and assign PAIR as assignee of subtask.png

Edit work item Fields - Pair to copy from Parent.png

Accepted answers

All comments

Trudy P Claspill

Hello @Glenn_Riley1

Please show us the details from the flow's Audit Log for an instance where this rule was actually triggered and you did not get the expected result. Make sure you click all the ">" characters in the Audit Log record to expand all the details available.

Also what is the Space Scope for this rule?

Without that information one possible cause is that the parent issue has no value in the "Pair" field.

Another possibility is that the Flow Actor doesn't have permission to Assign Work Items in the target project.

Tinker Fadoua

@Glenn_Riley1

Do you mean when customer field = Pair assign the subtask to QE Testers?

Do you have the field on the parent issue? So based on your condition it will get inherited by the subtask.

Some elaboration would be very helpful to better assist you.

Best,

Fadoua

Glenn_Riley1

The custom field is PAIR found on the parent Bug issue,

I want the subtask of this parent to auto populate the ASSIGNEE field on the sub task to be the same as the PAIR field on the parent.

Trudy P Claspill

I want the subtask of this parent to auto populate the ASSIGNEE field on the sub task to be the same as the PAIR field on the parent.

In the rule image you have shown you are using the Edit action to set the Pair field, not the Assignee field.

Screenshot 2026-07-23 at 7.38.16 AM.png

Instead use the Assign Work Item action.

Choose the Smart Value option and enter the Smart Value for the Pair field from the issue that triggered the rule (the subtask's parent).

Screenshot 2026-07-23 at 7.42.41 AM.png

Glenn_Riley1

Current setup of automation - based on feedback:

Parent issue in defined, moved from backlog -

Subtask remain unassigned - PAIR field on parent is populated ( legit value)

Subtask did move to define status from Open status as expected

Assign work Item - Smart Value 7 23 11AM.png Audit Flow 7-23 11 AM.png Automation Design 7 23 11 AM.png Parent of subtasks - still unassigned , 7 23 11AM.png

Trudy P Claspill

Hello @Glenn_Riley1 Are there any steps in your flow beyond what you have shown in the image you provided?

In the Log file is has a message for your branch about not finding any updated issues since the last time the rule ran.

Audit Flow 7-23 11 AM.png

Please provide an image showing the details of the Branch/For step.

Glenn_Riley1

No additional steps in the flow

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