Skip to content

Sort releases by semver in the "Resolved In" version selector #119886

Description

@dalnoki

Problem Statement

In the version selector shown when resolving an issue in a specific release, releases currently default to publish date ordering rather than semantic versioning.

This causes visual confusion when older build numbers are published after newer ones - for example, a customer seeing release@1.0.0+144136 appear above release@1.0.0+144150 simply because the former was published more recently.

Solution Brainstorm

No response

Product Area

Releases

Metadata

Metadata

Assignees

No one assigned

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Waiting for: Support

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions