Flagsmith / Flagsmith/flagsmith

UX Audit - Add optional descriptions to multivariate options

Open
#3,494 0 comments 0 reactions 2 assignees Claimed by @matthewelwell View on GitHub
api ux audit
Dominant language
Python
Stars
6.6k
Forks
567
Avg merge
1d 13h
Merged PRs (30d)
121

Description

### Is your feature request related to a problem? Please describe.

Variation values can either act as the name of the variation (like version “a” and “b”), or act as the values of what’s different in the test (e.g. the color of the button for each variation). But I only have one value to set, rather than separate name and value fields.

### Describe the solution you'd like.

![image](https://github.com/Flagsmith/flagsmith/assets/8608314/59a1957b-c374-458f-8663-1274834bbff7)

Much like segment rules, we should let multivariate options have a description. This could get cluttered so I think we do exactly the same as segments in toggling this on or off

![image](https://github.com/Flagsmith/flagsmith/assets/8608314/4dfd6cf2-1ecd-4fa9-8d43-8ade8df734a7)
![image](https://github.com/Flagsmith/flagsmith/assets/8608314/600ecfb6-31b1-43f5-8200-667bfa02fa84)

### Describe alternatives you've considered

N/A

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.