Background: Currently, I have 50+ automation rules in place. Each of these rules, when triggered, attaches 3 labels to a newly created Jira issue type based upon a drop down selection (in this case, it's a drop down of 50+ clients; whoever creates the Jira issue chooses 1 client for whom the issue is being created). In other words "If client = A, then edit issue with label 1, label 2, label 3"
Example: If "Client A" is selected, the automation attaches 3 labels indicating 3 key items for us: For examples: "Joe" the client's manager's name - but it's NOT the assignee of the issue, "June" the month that the client onboarded to our company - this is done for billing purposes, and "Medium" the client's risk - this is a label and NOT the standard RISK field in out of the box Jira.
Problem: From time to time the client's manager will change or the client's risk will change. This requires us to then go into the automation rule itself and change the label(s) that will be attached to the issues the next time the automation is triggered. "One-offs" aren't that bad (Example, "Client B" changes from low to high), but when/if a client manager leaves our company or their role, that will require us to shift clients around to other managers. This can lead to 20-30 automation rule changes as we shift clients from one manager to another...
Question: Is there a way that I can simply have a sheet serve as a database so that when any client is selected, the rule will reference the labels that are listed on the sheet for that client? Or, is there a better way to simplify our label assignments?
Outcome desired: We want a faster and scalable way to update/change our label assignment rules. If we can employ a sheet (or something else) as our "database" then we could simplify our rules by simply updating the sheet when a client's labels need to change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.