How can i make taks for an epic for specific users

[gyorgyolah]

Hey,

So we create epic for release-es and for every epic wich has the release label i want to generate four task per person.  I want to hard code which persons are these. (around 20 people total) They are in four different projects.

What works now is i created a rule in every project and if an epic with the label is created

i create a task for every user for every task, it's like 20 task in one project. And if someone goes or comes i create or delete four actions.

Is there a better way to do this? 
Like in a advanced branch I can hard code the accountId-s of the users and interate trouh?

I can only have a label on the epic, and i need to hide who will get the task in the automation rule.

[Trudy Claspill]

Hello @gyorgyolah 

Welcome to the Atlassian community.

Are you creating the same 4 tasks for each person? Are the four tasks identical for every person, with the difference being the Assignee?

[gyorgyolah]

Hello, 

Yes. Exactly.

Thank you.

[Trudy Claspill]

Hello @gyorgyolah 

I have been working on a solution for this. The solution is not working on my instance, but it works for another user on their own instance.

I opened my own community Question to ask why my solution isn't working. You can follow along with that here:

https://community.atlassian.com/t5/Automation-questions/Iterate-over-csv-field-of-user-account-ids-create-issues-for/qaq-p/2854751

[Trudy Claspill]

Hello @gyorgyolah 

In the post I referenced, the community helped me find the problem. So this solution should work for you.

What issue event do you want to trigger this automation?

- Should it run when the Epic is created, if the Epic has the Label value that indicates it is an Epic for a release?

- Should it run when Labels on an existing Epic are changed, and the release Label is added?

- Do you want it to run manually?

After you get past the trigger and any conditions you want to apply to the trigger issue (like checking that the issue type is Epic and the Labels field includes the specified Label), the structure of the rule would look like this:

In the Create variable action provide a comma separated list of the Atlassian Account IDs for the users for whom you want to create issues. You can get the users' Account IDs by searching for the users from the Team menu, and then pulling the ID displayed for them in the URL when you click to display the user.

The branch is created by selecting "For Each" then "Advanced branching".

Be very careful to enter the Smart Value correctly, and make sure where I have used varUserList you use the exact name of the variable that you specified in the previous step. This is case sensitive.

Use a Create Issue action for each issue in the set that you want to create for each user. If you want to create 4 issues for each user, use 4 Create Issue actions.

Select the fields you want to set. At a minimum you will be required to fill in the Summary field, and you'll need to set the Assignee and Parent fields. To set the Assignee field you will need to type in the smart value that you specified in the Branch step as the Variable Name. That will be case sensitive so make sure you match exactly what you put into the Branch step.

[gyorgyolah]

Hello Trudy,

What color your statue should be?

Thank you! 

It's works like wonder.

For now it's only when an epic created with the label. That part is okay.

Sincerely,

György Oláh

[Trudy Claspill]

I'm glad I could help you. I'm not sure I understand your question: "What color your statue should be?"

Can you provide more context for that question?