...
- Review new bugs and ensure they are placed with the correct project, dev team, and PO
- Give an initial prioritization ranking
- To gather from the PO or the dev team a release target so the issue is not lost
- To ensure that progress is being made within a reasonable timeframe
- Ping Pos for updates and other needed details
- To follow up on existing tickets
- Bump priority for long-outstanding issues
How the Support SIG prioritizes issues
- Criteria (P1, P2, P3, and P4)
- Patron facing
- Prevents daily work
- Involves finances
- Affects many institutions
- No progress for a long period (bump up +1)
How development teams prioritize issues
- Support SIG advice on the priority. The decision is taken by the PO for the given development team
- The community’s capacity plan designates 40% of development time to bug fixes