How to auto assign stories, tasks, subtasks, bugs to parent Epic Assignee?

[BenWade]

• This is what I used:

https://imgur.com/GLPvnjd

Unfortunately, it doesn't work and gives me this:

https://imgur.com/rLGi8Ui

Please, help me someone with this issue. Why Jira is so complicated I don't understand. It should be super easy to auto-assign to parent assignee. Isn’t it obvious that the same person who will work on an epic will also be responsible for stories, etc.

[Trudy Claspill · Accepted solution]

Hello @BenWade 

First, it is not obvious that the person assigned to an Epic will also do all the work under the Epic. Epics are often large pieces of work that can take a longer period of time to complete and may have many people contributing to the work needed to complete the Epic.

Second, addressing why your rule says "No Actions Performed"...

The trigger for your rule is "Issue Created" and you have followed that with the condition to check that that the issue created was an Epic. Your rule will run only when a new Epic issue is created.

Since the Epic is newly created it can't possibly have any child issues under it yet, so it can't copy anything from the Epic to the child issues.

If you want to copy information from a parent Epic issue to its child issues, you have to have a rule triggered by the creation of the child issue.

This is the rule you would need to copy the Assignee from the parent Epic to the child issue when the child issue is created.

To copy the Assignee of a child issue to its subtask when the subtask is newly created you would use this rule.

What about the scenario where the Assignee on the Epic is changed? Do you want all the child issues and subtasks updated? In that case you would need a rule triggered by the change of the Assignee field on the Epic.

[BenWade]

Dear Trudy,

thanks for your detailed response. It is unlikely that assignee on the epic will be changed. However, it is possible that more people will be assigned to a new  epic. For that purpose I created new field called “Multiple Assignee” because by default you can’t assign several people to one epic, which I find strange. Why only 1 person can be assigned? It’s good that you mentioned it. Could you please show me a complete automation rule with these two fields: “Assignee” and “Multiple Assignee”. For instance, it can be that I assign 1 person to one epic and 3 persons to another epic. In this regard, i want stories, tasks, subtasks to be assigned to parent “Assignee” or “Multiple Assignee”.

https://imgur.com/cVtqqJc

Thank you in advance for your help🙏

[BenWade]

I figured it out. 
It works perfectly.

[Nic Brough -Adaptavist-]

You say "by default you can’t assign several people to one epic, which I find strange. Why only 1 person can be assigned? "

An Epic is an issue.  You should never assign more than one person to an issue because it is an utter disaster in managing your issues.

But also, an Epic is a grouping of potentially thousands of issues.  It makes no sense to assign anyone to an Epic, unless it is the head of the division responsible for delivering the Epic, and that is likely to be someone who will not be assigned any issue within it.

Glad you worked out how to work with a multiple people-to-talk-to-about-this field though!

[BenWade]

Before Jira, my team has been using Ms Planner and List(no hierarchy, hard to track). We don’t have thousands of issues. There are 8 of us in the BI department and it isn’t software development but rather business analytics. It is super common when 2 people are working on a story or task and I want to indicate both of them in the assignee field 

[Trudy Claspill]

Hello @BenWade 

I'm glad you worked out the changed needed to copy the second field.

If the Answer provided helped you solve your requirement, please consider marking it as Accepted to help other users find posts with validated solutions.

[BenWade]

edit:

done. Nvm