Based on the field combinations I have to automatically assign the user. But here I have 5000 combinations . How can I solve it.
Hello @sravani vennapusa
How many fields are being evaluated? How did you arrive at the total of 5000 combinations?
Are the fields selection lists? If so, how often do the available values change for these fields?
When do you want to evaluate the field values to make the Assignment? Do you need to reevaluate any time one of the fields' values is changed?
This is not something that can be readily solved by native Jira capabilities. Are you willing to consider acquiring a third party app for this. What third party apps do you already have?
Do you have the Assets app available to you? Assets might be a solution depending on the field types being evaluated.
Thanks for reaching out. managing 5000+ combinations to drive assigning work may prove difficult. Instead, you may wish to think about it from what rules would drive a piece of work to one user versus another.
This may help you to narrow down what conditions lead to an assignment to a user. For example
User 1: Will always be assigned work with a value set of <5
User 2 Will always be assigned work with a value 6+
User 3 will always be assigned work with no value
etc...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Before suggesting a path — could you share how many actual fields drive the assignment, rather than the number of combinations?
The combinatorics can be misleading here. If Field A has 3 values, Field B has 6, and Field C has 7, that's already 126 combinations from just 3 fields. 5000 combinations could realistically come from 4–5 conditional fields, which is a very different problem from maintaining 5000 individual rules.
Once that's clear, the assignment logic doesn't need to live in a giant lookup table. It can usually be expressed as conditional logic on a handful of fields — either via a scripted post-function / automation rule on the server side, or via field-level behaviours / UI Modifications on the client side if you want the assignee to update live as the user fills the form.
Which fields are driving the assignment, and roughly how many distinct values does each one have? If you can share a bit more detail on the fields and how they map to assignees, I'd be happy to put a quick showcase of how this can be solved with a behaviours-based approach.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @sravani vennapusa
First, please describe your process and use case in more detail.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.