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

JSON help with automation of field Team

Karolina Yeong

I've been trying to set an automation for field Team that is used by advanced roadmaps. I want to automatically set child issue Team to be same as Parent. With below JSON code the automation runs successfully, but the issue field is not being populated.

{ "fields": { "customfield_10001": "{{issue.parent.customfield_10001}}" } }

In my automation I have also included a log to see if the parent Team is read OK, and the log shows: Parent Team value: d458a753-47c4-4fde-ae80-63304af11702.

I also tried to directly enforce above Team to the issue being created but this also ends up in field not being populated. How can I force the child issue field to populate?

Accepted answers

Trudy P Claspill

Hello @Karolina Yeong

Welcome to the Atlassian community.

Is this you current rule?

If so, this will not achieve your goal.

With the branch "For Parent" you are shifting the focus of the rule from the trigger issue to the Parent of the trigger issue. Actions that you take inside of the branch will affect the Parent issue, not the trigger issue. Within the branch use of the {{issue}} smart value will refer to the Parent issue, not the trigger issue.

You initially said you had a rule that included the Log action to print the value of the Team field. Can you revert to that version of the rule and show that to us?

All comments

Karolina Yeong

This is what I have so far:

When a child issue is added to parent, I want the child issue to inherit Parent's Team.

Vishal Biyani_2pr07j

@Karolina Yeong

In the edit issue field, you can use copy Teans from parent. You may not need to branch to parent as long as it is ensured parent has Teams field populated

Karolina Yeong

@Vishal Biyani I've updated my post with latest findings. I can run automation OK now, but the field isn't being populated on trigger issue.

Trudy P Claspill

Hello @Karolina Yeong

Welcome to the Atlassian community.

Is this you current rule?

If so, this will not achieve your goal.

You initially said you had a rule that included the Log action to print the value of the Team field. Can you revert to that version of the rule and show that to us?

Karolina Yeong

This is what I have now:

the log returns: Parent Team value: d458a753-47c4-4fde-ae80-63304af11702

Karolina Yeong

@Trudy P Claspill the suggestion of removing the branch seems to have done the trick! I was trying to use the Jira AI assistant and this is where the branch had come from

Brian Duchek

Did you make any progress here? I've got the same issue. It can read an existing value, but can't set it.

Trudy P Claspill

Hello @Brian Duchek

The author was able to solve their problem based on the responses I provided. You can see those higher up on the screen, under the lozenge that says Answer Accepted.

Since this post already has an accepted answer, if that solution does not help you solve your issue, please start a new Question thread by clicking the +Ask a question button at the top of the screen.

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