UX Audit - Improve the trait input field when creating segment definitions

[dabeeeenster]

The trait field:

Should be better/more intelligent. It should be a combined autocomplete/dropdown/free text element.

Populating the drop down

With the global API this is going to be tricky as we don't store a canonical list of trait keys. A 99% solution would be to grab ~50 identities at random and create a list of distinct trait keys from that data. This would be a significant improvement over the current implementation.

We would need to create an API endpoint to return this list.

[kyle-ssg]

Theres already an endpoint that would allow this, environments/:id/trait-keys/ but I guess we need that on the project level?

[dabeeeenster]

Hmm yes - and also this data is not going to be accessible when we deploy the Global API. Needs some thought on how we can keep a list of distinct trait keys within a project cc @gagantrivedi @matthewelwell

[kyle-ssg]

Ah, this will be a breaking change to the frontend in that case, we display global traits in the users list page

[dabeeeenster]

Started a discussion at #437

[kyle-ssg]

I'll need API before I can work on this

[agerlic]

Hello, is there are any updates regarding the resolution of this issue?

[dabeeeenster]

We're not currently working on this feature I'm afraid. It's technically complex with our Edge API.