I wanted to introduce a "Client" field which will act as a pivot to tell the plugin what set of business approvers needs to be notified. Currently, I have to have an issue type created per client in which I need to make 6 separate approval mappings per client in accordance to our workflow.
If it was possible to set an approval mapping on a certain field other than project and issue type I would be able to cut the mappings by 4 for every client I need to set up.
Sorry for the late reply.
Let's say I have 3 clients of which our teams work on to support. Said teams total to about 6 (development, qa, operations, etc...). Usually (at least in our scenario), the actual approving people within those teams are the same across clients but not all. Ideally, I would have the following setup:
As of now, the Approval Mapping Administration UI limits me to project-issue type mappings to configure in these teams. This in turn forces me to make client-specific approvals as well as issue types for the teams even though the people inside those teams are the same. Thus I've made this work for me by doing this:
(Request type (Standard/Emergency Normal) is a separate custom field here)
This involves a lot of duplication though and it results in a number of issue types and approvals that will be generally unused throughout the JIRA ecosystem
Therefore if there is a way to change an approval mapping from being dependent on a project-issue type combination to lets say a project-custom field combination, I'd be able to achieve the first scenario without much clutter.
Hope this makes this question clearer.
In order to setup your configuration on one issue type, instead of three, you can setup three Approval Mappings with Conditional Rules on three transition (one for each client) from/to the same workflow statuses.
The following screenshots illustrate the suggested configuration.
"Customer Name" ~ "Client 1"
"Customer Name" ~ "Client 2"
"Customer Name" ~ "Client 3"
Where the Customer Name is a custom field that identifies the customer.
I hope it helps.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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