nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I auto assign based on the parent issue's project/project key?

ngwako.mphahlele

Hi,

Please help me solve this.

I am trying to auto assign to certain users using the parent issue's project.

When a Feature is created, it spawns a Task. The task must then be assigned to a certain user which is determined by where/which project the Feature comes from. If the Task is spawned by project A, it should be assigned to user A. If the Task is spawned project CAB, it should be assigned to user B.

The parent Feature's project should determine who the child Task is assigned to.

Is there a way to achieve this?

Thank you

Accepted answers

Antuan Sammak

Hi @ngwako.mphahlele

Welcome to the Atlassian Community!

you can try implement something similar to the below through automation and it should work, of course in the branch you can add multiple conditions per project.

All comments

Antuan Sammak

Hi @ngwako.mphahlele

Welcome to the Atlassian Community!

you can try implement something similar to the below through automation and it should work, of course in the branch you can add multiple conditions per project.

ngwako.mphahlele

Hi Antuan,

Your response is appreciated.

However, it's missing some crucial bits. Which might be my fault. Let me try explain a little clearer.

Let's say there are 10 projects, A to J. The project we are focusing on is J.

Anyone from projects A to I can create a Feature, that Feature will spawn a Task on project J.

The Features are all created from and belong to projects A to I.

The users on project J find Tasks already created for them. All that needs to happen from this point is auto assigning Tasks on project J to the relevant users depending on the Features that were created on project A to I. The task spawned from project A's Feature needs to be assigned to user 1. The task spawned from project B's Feature needs to be assigned to user 2 and so forth.

Would the automation look a little different with that info

Antuan Sammak

Hi @ngwako.mphahlele

Apologies if i misunderstood your question in the first time.

here is the updated rule, you need to use if/else type of condition....first "if" will be project A and type feature then else project B and type feature and so on until I

for each condition the action would be to create a task or subtask (doesnt matter, depends on your case but a subtask would work better so its linked to the feature automatically, otherwise you need to add the feature ticket as Linked ticket to the task one)

also in the step of creating subtask you can set the user according to the condition

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud