Multiple component assignees?

[Chris Weiss]

We have a task workflow that is essentially Defined->Approved->In Progress->Complete. The work is Component centric, with there being an Approver assigned to each Component and a Worker assigned to each Component.

In Jira, we have the Approver set as the Component Lead, and an approval button. When a new ticket is Defined, it's assigned automatically to the Approver (Component Lead).

What we'd like (and can't figure out how to implement) is for, when the Approver moves the ticket to the Approved stage, it automatically assigns the ticket to that Component's Worker.

This can hardly be a unique need - How are other folks managing this flow?

[Timothy · Accepted solution]

You'll need to have some kind of custom workflow post function that picks up on the component aspect and assigns it to the right person.

[Chris Weiss]

Gotch - Our issue is how would we define/maintain both an Assigner<->Component relationship and a Worker<->Component relationship? In our Jira instance, it looks like you can only have one 'user' associated with a given Component (the Component Lead).

We can't use Project Lead as that's not per-Component.

I suppose we could create a big script that manually does it per-Component, but that will be very unwieldy (Components/Approvers/Workers change often).

[Peter Van de Voorde]

Hi Chris,

Can't your approver simply assign it to the worker? I suppose they will know who's who in this kind of setup. It will be less messy than forcing it to automate.

Best regards,

Peter