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?
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).
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG