Increasing the scope of team triage packages to include more types of issues
We are proposing to change up the triage packages to encompass further types of team issues. We can
- Merge the results and summaries from several triage package rules targeting different types of issues (~"feature proposal", frontend ~bug, backend ~bug)
- Utilise multiple assignees for issues to assign a different team member for each of these rules
- Each rule can have a separate summary explaining the actions required for the issue type
- For bugs S/P labels are required
- For feature proposals, feasibility of the feature should be studied and the issue possibly scheduled, left to gain further traction or closed down
The current triage package indexes bugs for the team.
The new triage package should index in separate sections:
- Team feature proposals
- Team frontend bugs
- Other team bugs
This fall in line with the current triage flow.
- New issues are triaged by the triage team via the new, unlabelled triage package
- Triaged issues are picked up by the team level triage package
Because we will be assigning the new triage package to several team members we can include a larger number of issues in each package