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

Question

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

* Task/Story is created (working ✔️)
* Check in Epic to see which Team it has (not working ❌ )
* 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.

timothy.higgs.extern · Answer

Thanks Christos but unfortunately, I have never used the audit log or set variables myself and I'm a little out of my depth here. 
Doesn't help that our Jira instance is in German and not all the actions translate well from English.

Could you perhaps, either: 
1. Post a lot more detail about how you're filling out each of these steps? In particular, which information goes in which field? That would be a huge help, but yes, a fair bit of effort for you. 
OR
2. Do you know of any resources, or how-to videos that could help me learn how to do this? 
I have found literally nothing that explains how to use the audit log to create, store and use custom variables. Only lots of courses and videos about Jira Automations in general.

Thanks so much
- Timo

Christos Markoulatos -Relational- · Answer

Now this was a weird one but made it work like so

I solved this by creating a Jira Automation rule that copies the Team field from the parent Epic to a Story or Task. The key is variable scope: variables created inside a branch don’t persist outside, so you need to declare the same variable name both inside and outside the branch

* Trigger

* Manual trigger (you run it on a Story/Task).

* Condition

* Issue type is Story or Task.

* Create variable (main scope)

* epicTeamid (initially empty or placeholder).

* Branch: For Parent (Epic)

* Inside branch:* Create variable epicTeamid = {{issue.customfield_10001.id}} (Epic’s Team ID).
* Log {{epicTeamid}} (to confirm value).

* Back to main scope

* Create variable teamtrimmed = {{epicTeamid.trim}} (removes whitespace).
* Log {{epicTeamid.trim}} (audit check).
* Edit issue fields:
* Json: {
"fields": {
"customfield_10001":"{{epicTeamid.trim}}"
}
}

timothy.higgs.extern · Answer

@Christos Markoulatos -Relational-  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