Variable matrix of approvers. How would you handle it?

[Stephen Hayden]

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?

[Stephen Hayden · Accepted solution]

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