inherit the value of the 'account' field from the epic and put it in each task of the epic

[KALOS]

In a Jira project, I have associated several Tempo Timesheets accounts. I would like to make sure with automation for jira, that when I create an epic and associate the epic with one of the accounts, let's say Account1, all the tasks I create within that epic will then take the value of the account field of the 'mother' epic. Have any of you faced and solved this problem? At the moment I can't and so I have to make a rule for each epic ... in the project. Specifying the account code by hand.

[Dick · Accepted solution]

Hi Kalos,

You would end up with two automations:

First one:

The start of your automation should follow your problem description:

when: Field Account changes on an issue

And the issue is an Epic

Branch for all issues in Epic

Then edit issue field Account = value copy from epic

Second one:

If the epic is already there and an issue is linked to the epic:

When: value changes for parent link 

and issuetype in (story, bug, etc)

and parent link is not empty

edit issue fields Account = copy from parent

[Dick]

to be neat: you would require the reciprocals as well (might be able to build them into one and two).

Third one:

if an epic looses the field account the attached issues should be loosing the field content as well.

Fourth one: 

If an issue is taken from an epic it should loose the corresponding value for Account.

Life is never easy, building automations as well... 

:)

[KALOS]

the third case in my management process, is not covered. While the fourth is interesting, of course. But for now I'm 'stranded' in understanding: how do you tell automation for jira to 'read' the account field in the epic and pass it to the linked task?

[KALOS]

ok @Dick I did not see your suggestion point two properly. So I have to do that? and how do I say 'take the account field then'?

[Jack Brickey · Accepted solution]

Hi @KALOS , welcome to the community.

Could you please share the audit log associated with the rule triggering? Another thing that you're going to need to consider here, after we get the basics working, is that an issue could be added to the epic after it has been created so I think you're gonna wanna trigger on the issue being updated and the Parent feel being set. Likely a separate rule.

[KALOS · Accepted solution]

Reflecting on the suggestions you have given me I finally solved it this way, for now I am only fine with handling the case of the newly created task under the already existing epic. Thank you both.

[KALOS · Accepted solution]

@Dick @Jack Brickey   Yes, you are right, I am only examining one case so far. But let's look at this case: I already have an existing epic which already has the 'account' field valorised. And I want to create many tasks in the epic. How do I set up an automation rule that 'understands' what the epic is and copies the 'account' field from the epic to the task I'm creating? Then maybe from some examples you can give me, I'll try to make rules for the other cases too. For Jack, I didn't understand what you need the audit log for. 

[Dick]

Hi Kalos,

Thank you for accepting my answer / way of thinking. Be sure to turn the automation off when you're done creating the tasks under your epic, as you're running the automation for each issue created (also when it isn't attached to your epic).

Your last question is answered in script two.

Happy automating!

Dick