Skip to content

Open issues parked in closed milestones are invisible to every milestone view #1048

Description

@gaurav

Roughly 253 open Babel issues sit in closed milestones. Closing a milestone does not detach its issues, so these are absent from every milestone view while appearing handled.

Counts at the time of writing:

Closed milestone Open issues
Needed soon 87
Needs tests 54
Needs investigation 46
Immediate 27
Needed later 25
Translator June Hackathon 2026 9
Improved testing 3
Needs review 1
Fish Notes Cod Burst 1

That is over half of Babel's ~482 open issues. TranslatorSRI/babel-validation has one more, in the closed Babel Validation January 2024.

Noticed while building the cross-repository milestones page (TranslatorSRI/babel-validation#112), which reads open milestones only and so does not show any of these.

Needs a decision on whether they are re-triaged into current milestones or bulk-detached.

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

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions