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.
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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs