Search Identities Display By Alias or another field
complete
M
Minimum Caterpillar
When selecting individual targets for a feature flag, the identifier key of the target is shown. This key will typically be some durable key, mapping from maybe a monotonically incrementing database value (surrogate key) or some other globally unique identifier (GUID, ULID, SnowflakeId). While identifying by key is good, managing by key only does not seem very user friendly. Ideally, we'd be able to display some other friendly field alongside the id so that our product people can add and manage the targets without having to do an id lookup.
Photo Viewer
View photos in a modal
Log In
d
david.karow
marked this post as
complete
This feature already exists, but was blocked by a UI bug which was resolved 4/16/26. A new CSV upload utility has been been created to streamline usage of this feature. Documentation will be published soon. In the meantime, please reach out to david.karow@harness.io for early access to the draft docs and upload utility.
d
david.karow
Photo Viewer
View photos in a modal
d
david.karow
Merged in a post:
User friendly label for traffic keys in UI
Johannes Liegl
For UI and targeting purposes, having a "friendly" name that teams can use to identify which client they're targeting would be great. Currently they're getting around this by creating segments of only 1 ID to help them identify IDs with an easy to understand label, but it's more of a workaround than an actual solution.
d
david.karow
Merged in a post:
Search Identities Display By Alias or another field
N
Night sky Dolphin
When selecting individual targets for a feature flag, the identifier key of the target is shown. This key will typically be some durable key, mapping from maybe a monotonically incrementing database value (surrogate key) or some other globally unique identifier (GUID, ULID, SnowflakeId). While identifying by key is good, managing by key only does not seem very user friendly. Ideally, we'd be able to display some other friendly field alongside the id so that our product people can add and manage the targets without having to do an id lookup.
M
Minimum Caterpillar
Adding more business context from a recent enterprise request.
The Business Problem:
Currently, project managers and product owners must maintain a manual "translation layer" between Harness IDs and their internal business tools. When toggling flags for a specific client, they have to cross-reference system-generated GUIDs or numeric IDs to confirm they have the right target. This is a primary source of operational friction and risk during releases.
The 'Org Pin' Use Case:
For large entities that manage multiple sub-entities, they use an 'Org Pin' as a grouping mechanism. Users need to see the friendly name of the Org Pin or the client directly in the FME UI to avoid toggling flags for the wrong release wave or application version.
Specific Ask:
- Display a friendly metadata field (e.g., alias, name, or org_pin) alongside the unique identifier.
- Enable searching and filtering by these friendly fields in the target selection dropdown.
This would significantly lower the barrier for non-technical users to safely manage rollouts.
Photo Viewer
View photos in a modal
N
Night sky Dolphin
Photo Viewer
View photos in a modal