...
The prioritization process:
Subteam members are assigned Jira The co-leaders regularly survey Bug and Feature Request Jira tickets and assign subteam members tickets to investigate and discuss at the team meetings. In preparation to the meeting, subteam members verify the issues, seek/provide clarification when needed, and screen for duplicates, obsolete issues, or institution-specific technical issues that should instead be addressed locally. During the meeting, the subteam discusses the tickets, reevaluates the priority ranking, and will route the ticket to “Awaiting More Information,” “Ready for Implementation,” or “Closed” if the ticket is declined. Subteam The subteam member assigned to the ticket will follow up with explanatory comments on the decision. Each meeting tries to address a mixture of Bug and Feature requests, from both the “Awaiting Prioritization” and “Awaiting More Information” queues.
...
- Demonstrated community interest in the issue by supporting votes and comments on the tickets and/or discussion on the member listserv and Google Group
- Sufficient specification (see the How to Request a new Feature/How to Report a Bug documentation and Hydra Project)
- Developer capacity and expertise
- Priorities outlined in the Development Roadmap
- Results of the Development prioritization survey (last issued July 2016)
...