Variable matrix of approvers. How would you handle it?

So I have a project where each ticket may require any number of 20 or so approvers from across the company. The request will be received and the triaged and each of those selected will be notified, and each should be able to come and approve the ticket. I can think of some really ugly ways to handle it (each user w/ a custom field, setting that field to approved/denied/null, and a ridiculous set of conditions) but was wondering if there was a better way.

A friend has done some approval work with https://marketplace.atlassian.com/plugins/com.fca.jira.plugins.workflowToolbox.workflow-toolbox so I might tinker with that a bit before embarking down conditional hell.  Tickets will be created by default UI or Service Desk.

Thoughts?

1 answer

1 accepted

Accepted Answer
2 votes

Found this example which is what I'll probably start from using the referenced plugin.  Not super keen on creating 20 project roles though.  Sometimes I really wish those were project-specific.

https://bitbucket.org/fcarmario/jira-workflow-toolbox/issue/117/possible-solution-for-a-multi-approval

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

21,082 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you