List view
Testing period: June 22 - July 10
Due by July 10, 2026Final sprint before release testing
Due by June 19, 2026•0/3 issues closed- Due by May 29, 2026
- Due by May 8, 2026•0/8 issues closed
- Overdue by 2 day(s)•Due by April 17, 2026•0/12 issues closed
- Overdue by 23 day(s)•Due by March 27, 2026•2/10 issues closed
- Overdue by 1 month(s)•Due by March 6, 2026•3/5 issues closed
- Overdue by 2 month(s)•Due by February 13, 2026•8/11 issues closed
- Overdue by 2 month(s)•Due by January 26, 2026•6/7 issues closed
- Overdue by 4 month(s)•Due by November 26, 2025•55/75 issues closed
- Overdue by 5 month(s)•Due by November 7, 2025•6/7 issues closed
- Overdue by 6 month(s)•Due by October 10, 2025•3/3 issues closed
- Overdue by 7 month(s)•Due by September 19, 2025•6/6 issues closed
- Overdue by 7 month(s)•Due by August 29, 2025•10/11 issues closed
- Overdue by 8 month(s)•Due by August 8, 2025•5/5 issues closed
- Overdue by 10 month(s)•Due by June 13, 2025•5/5 issues closed
All bugs created in this milestone are relevant to the Q2 Release QA SORMAS Foundation week (June 16-20) Process: 1. Testers create bugs in this milestone 2. Jan, Obinna, and Emeline to triage bugs - meet EOD to review bugs, prioritize and assign. 2a. Categorize: 1) Critical for release 2) If no, remove from milestone and add to backlog, document for known issues 3. Emeline to assign bugs to SORMAS kanban board 4. Developers work through kanban board as normal
Overdue by 9 month(s)•Due by June 25, 2025•48/48 issues closed