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?

[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

[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]

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.

[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.

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).

[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.

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

[Glenn_Riley1]

No additional steps in the flow

[Trudy P Claspill]

I am not able to reproduce your issue. And I have not found any other reports of this problem.

Can you try recreating your rule from scratch and see if it still happens?

If it does, rather than using the For: Children option you can use the Branch: Related Issues: JQL option.

[Glenn_Riley1]

Updated Work flow  still not update the assignee , status is getting changed to Defined when status of Parent is moved to Defined

[Trudy P Claspill]

Thank you for the additional information @Glenn_Riley1 .

What type of field is "Pair"?

What information is shown in the flow log file? Click all the ">" characters to expand all the details and share a screen image with us.

Prior to the Assign the work item step and a Log action. In the Log action enter the smart value you are using in the Assign action. That will print out the value that is stored in that custom field in the trigger issue, and you can manually confirm that it matches the value you see in the trigger issue in that custom field.

[Glenn_Riley1]

Pair is a field were we select a quality tester to be assigned to testing the issue.

I believe it is a custom field, not everyone uses it.

I it ran the automation on an issue and both status and assignee worked.

[Glenn_Riley1]

[Trudy P Claspill]

Hello @Glenn_Riley1 

I am a unclear about what you are trying to convey with your last replies.

Are you saying the rule works exactly as you want, now? If so, that's great!

I ask because in the last image of your rule you have replaced the Assign Work Item action with the Edit Work Item action. But the Log you have shared indicates that the rule should show an Assign Work Item action.

If you are still having difficulty let us know. And in that case please share a screen image that shows your rule and a screen image for the audit log that was generated by the execution of that rule.