Skip to content

[REQUEST] Clarify status chips for manually promoted release-track members #954

Description

@jondricek

Is your feature request related to a problem? Please describe.
When auto-promote candidates is disabled for a standard release track, objects can be manually moved from Candidates to Staged. The object’s status chip (for example, “Work in Progress” or “Reviewed”) can conflict with or be confused for its release-track column, making its place in the release workflow unclear.

Describe the solution you'd like
Clarify the distinction between an object’s workflow status and its release-track state. Consider clearer labels, separate visual treatments, or contextual help so users can immediately tell both the object’s status and whether it is a Candidate or Staged member.

Describe alternatives you've considered
Users can infer the object’s release position from its column and its workflow status from the chip, but this is ambiguous when the labels convey different stages of readiness.

Additional context
This applies to standard release tracks with auto-promote candidates disabled, where manually staged objects may still have a “Work in Progress” or “Reviewed” status.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions