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

JIRA Automation: Copy "Team" Field from Parent (Epic) when a new child issue (Task/Bug) is created

mark.liebold

I am trying to set up an automation that copies the value of the "team" field from the parent (Epic) when a new child issue (Task/Bug) is being created.

Even though the documentation about teams says that you can now use the "team" field in automation, this is not possible when it comes to the "Edit Issue" action, the field does not show up in the selection menu.

For the action "Field value changed" the "team" field is available, though.

I am grateful for any advice that will help set up the automation. Thank you!

Accepted answers

Mayuresh Kamble

Hi @mark.liebold ,

Could you please try this in the edit issue action and let me know if it works

{
  "fields": {
    "team": "{{issue.epic.team.id}}"
  }

Regards,
Mayuresh

Ste Wright

Hi @mark.liebold

You can use the Advanced section and JSON to do this.

For example, to modify an Epic's children when the value changes at an Epic level...

Trigger: Field Value Changed
- Field to Monitor = Team
Condition: Issue Fields Condition
- Field = Issue Type
- Condition = equals
- Value = Epic
Branch: Related Issues
- Type = Children
  - Branch-Action: Edit Issue
    - More options...
      - Additional fields...
        {
        "fields": {
        "customfield_10001" : "{{triggerissue.customfield_10001.id}}"
        }
        }

---

A few notes...

The Custom Field ID (i.e 10001) should match your Team field's ID
This is just an example rule, with example JSON. It might differ depending on how the rule is triggered (eg. if it's issue created, or parent being set at a story-level, the JSON could use a smart value which references the epic's team field in another way)

Let us know what you think!

Ste

Thuan_ Do Dang

Hi @mark.liebold ,

You can try to update by Additional fields like below

Copy Team from parent.png

{
    "fields": {
         "Team": "{{issue.parent.Team.id}}"
    }
}

All comments

Mayuresh Kamble

Hi @mark.liebold ,

Could you please try this in the edit issue action and let me know if it works

{
  "fields": {
    "team": "{{issue.epic.team.id}}"
  }

Regards,
Mayuresh

Ste Wright

Hi @mark.liebold

You can use the Advanced section and JSON to do this.

For example, to modify an Epic's children when the value changes at an Epic level...

Trigger: Field Value Changed
- Field to Monitor = Team
Condition: Issue Fields Condition
- Field = Issue Type
- Condition = equals
- Value = Epic
Branch: Related Issues
- Type = Children
  - Branch-Action: Edit Issue
    - More options...
      - Additional fields...
        {
        "fields": {
        "customfield_10001" : "{{triggerissue.customfield_10001.id}}"
        }
        }

---

A few notes...

The Custom Field ID (i.e 10001) should match your Team field's ID
This is just an example rule, with example JSON. It might differ depending on how the rule is triggered (eg. if it's issue created, or parent being set at a story-level, the JSON could use a smart value which references the epic's team field in another way)

Let us know what you think!

Ste

Thuan_ Do Dang

Hi @mark.liebold ,

You can try to update by Additional fields like below

Copy Team from parent.png

{
    "fields": {
         "Team": "{{issue.parent.Team.id}}"
    }
}

mark.liebold

Thank you for the help, it worked!

mark.liebold

Thank you for the help, it worked. However, I went with "parent" instead of "epic" in the JSON.

mark.liebold

Thank you! I set up another automation where it was needed to change the "team" field in the children when it got modified in the parent and your advice helped me a lot.

Margarita Turina

Hi!
Unfortunately this didn't work for me - it says "Additional fields contains invalid field(s) in 'update' or 'fields' section: Team" - but I definitely have the "original" Jira team field, not a custom one.

Could you guess what might went wrong?

Ste Wright

Hi @Margarita Turina

Are you using the Custom Field's ID? Usually that's a more static option than the field name (just in case there's another Team field).

Otherwise, could you provide a screenshot of your Action?

Ste

Josh

Is anyone aware of a feature request to make this important "team" field available as a field to edit in automation?

The workarounds above are very helpful, but an admin shouldn't have to go through all the hassle to do something like this.

Bill Sheboy

Hi @Josh

There are several open suggestions related to adding the Team (and other missing fields) to the dropdown list for automation actions. Here is one of them:

https://jira.atlassian.com/browse/AUTO-525

Kind regards,
Bill

Josh

Thank you, @Bill Sheboy

wojtek_pawlak

Apparently this solution stopped working - JIRA makes us now to choose fields and do it from the UI, rather than from the code snippet in Advanced options. Is there any workaround?

SilkeS

This topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have additional questions, we encourage you to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our Community Guidelines.
Thanks!

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-software

jira-software-cloud