List view
Milestone for tickets that get closed as won't do (because are duplicates or obsolete in some way, ... or just not considered appropriate). This so they don't get counted as having been fixed as part of a release.
No due date•1/1 issues closedTickets where no implementation is yet obvious or agreed should be posted against this discussion milestone rather than a release milestone. Once there is agreement on an implementation, if appropriate the ticket could be moved or closed and an new issue created against an actual release milestone.
No due date•0/9 issues closedThis should be released in time for the next release of SasView post fall 2021 Hackathon
Overdue by 4 year(s)•Due by November 30, 2021•10/10 issues closed- No due date•23/111 issues closed
- No due date•0/4 issues closed
- No due date•11/54 issues closed
- No due date•4/13 issues closed