Settings and activity
44 results found
-
3 votes
Kristian Reich
supported this idea
·
-
11 votes
An error occurred while saving the comment Kristian Reich
supported this idea
·
-
6 votes
An error occurred while saving the comment Kristian Reich
commented
It would help to mitigate the effects of flag/rule sprawl as well. We have hundreds of flags and it can be difficult to find what you are looking for. Also would help users group by space so you can see all associated flags/rules together.
Kristian Reich
supported this idea
·
-
4 votesKristian Reich
supported this idea
·
Also need to have search corpus include variable datasets and values. When you have json for most variables, understanding what values exist in which variables is critical - especially when you have a large number of variables.
Alternate: allow user to include/exclude data sets to the search corpus so I could add variables to specific queries without impacting every other base data set and default queries don't have to include all to limit performance impact. By variable datasets I mean default it the smallest dataset, but, critically, allow me to expand my search radius when I need to. I don't always need to search history, but when I need it, I need it. I don't always need to search variant json, but sometimes I absolutely need to. In those cases, I select from drop-down to access/include those search corpus. Much like segmenting in reports.
Target data sets: flag names, flag descriptions, rules, audience, events, variables, variations, user actions (history), etc... ALL the things.