Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Copy "Team" Field from Parent (Epic) when a new child issue (Task/Story) is created

timothy_higgs_extern
Contributor
November 24, 2025

I'm having trouble with the first bit of this automation. 

 

  1. Task/Story is created (working ✔️)
  2. Check in Epic to see which Team it has (not working ❌ )
  3. Copy the Team to the Issue that was just created 

For some reason, when I try to check the Epic Parent Issue for its Team, it keeps checking the Task/Story that was just created. 

Here is what I've tried as conditions so far and none of them have worked:

  • {{issue.epic.Team}} equals (My Team's Name)
  • {{issue.epic.Team}} equals (My Team's ID)
  • {{issue.parent.Team}} equals (My Team's Name)
  • {{issue.parent.Team}} equals (My Team's ID)
  • {{issue.parent.customfield_XXXXX}} equals (My Team's Name)
  • {{issue.parent.customfield_XXXXX}} equals (My Team's ID) 
  • {{issue.epic.customfield_XXXXX}} equals (My Team's Name)
  • {{issue.epic.customfield_XXXXX}} equals (My Team's ID) 

I have tried also with all lower case and all camel case. I've tried encasing the Team Name in " " quotes. 

None of this has worked. When I check the audit it says that it's checking in the newly created Task/Story for the Team and not in the Parent Epic. And of course, there is no Team in the newly created Task/Story.

If anyone can help I'd be very very grateful! 🙏🙏🙏 

-----
UPDATE: 

Perhaps it's also relevant, that I was able to get this automation to work when it's a Sub-Task created and you have to check the Parent Task/Story. ALTHOUGH...in the Rule Audit is says it's not working. But when I create Sub-Tasks, the Sub-Tasks are properly given the right Team. Aaahh so strange! 

But for some reason, when I'm trying to check a Parent Epic, it's not working. Audit says No and no Team is assigned to the Child Story/Task. 

 

 

 

 

 

 

1 answer

0 votes
Christos Markoulatos
Community Champion
November 24, 2025

Hi @timothy_higgs_extern 

What i believe is happening 

{{issue.epic.Team}} and {{issue.parent.Team}} only work in certain contexts:

  • issue.epic works when the trigger issue is a Story/Task linked to an Epic.
  • issue.parent works for sub-tasks, not for Epic → Story relationships.

When your rule triggers on “Issue Created,” the smart values refer to the new issue, not its parent. That’s why the audit shows it’s checking the child issue.

You need a Branch in your automation to look at the Epic and copy the field

timothy_higgs_extern
Contributor
November 24, 2025

@Christos Markoulatos  thanks for the reply. 

The problem I run into when I create a branch to look at the Epic, is that I can't seem to then find a way inside that branch to update the team of the newly created Task/Story. I'm only able to edit the Epic because I'm looking at the Epic. 

I'm hoping there is a way to do this and I just don't know it yet, but I haven't found a way yet. 

Do you know how to do this?

I've included a screenshot and added translations cuz our Jira instance is in German

Thanks muchly

Screenshot 2025-11-24 163431.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events