For example, I want to experiment with the routing process for a targeted segment of JIRA tickets to see if a new process outperformed an existing process. We would want to randomly split the ticket cohort (say 50/50) and then apply a routing or handling condition to the treatment group. Then we would measure the impact of the treatment vs the control group to see the impact of the new process. If the new process proved successful, we would deploy the workflow change.
The only tool I've found that hooks deeply enough into the JIRA workflow function would be to leverage JIRA automation to split tickets by evens and odds but that doesn't provide the flexibility and random sampling we're looking for.
Any ideas??
Options for storing A/B groups
Implementing A/B features in workflow
Transition Conditions will hide/show actions depending on membership in the A/B groups.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.