High-priority tickets
Priority: blocker (1 match)
| Ticket | Summary | Status | Owner | Type | Priority | Milestone | Component | Keywords | Size |
|---|---|---|---|---|---|---|---|---|---|
| #262 | Over the summer, moira classifies students as "affiliates" | new | defect | blocker | Sometime | People | small | ||
Priority: major (4 matches) |
|||||||||
| Ticket | Summary | Status | Owner | Type | Priority | Milestone | Component | Keywords | Size |
| #42 | Account balances in the database | new | enhancement | major | Sometime | Funding | impacts:sao, impacts:funding-boards | medium | |
| #55 | Smarter navigation menus | new | enhancement | major | Near Release | Infrastructure | impacts:groups | large | |
| #244 | Label dev sites | new | enhancement | major | Sometime | Infrastructure | small | ||
| #248 | Make derecognized status more obvious | new | enhancement | major | Sometime | Core | tiny | ||
Bugs
Type: defect (11 matches)
Quickies
Size: small (27 matches)
TicketsByComponent
Consider picking a component that seems interesting, and going through as many of that component's worthwhile-looking tickets as you can.
TicketsByMilestone
Alternatively, look at the milestones coming up (or past) and deal with their tickets.
Last modified 13 years ago
Last modified on Mar 7, 2013, 2:28:46 PM