We are overdue for a graveyarding review of our community issues in Jira, where we review and close issues that have not been updated in >1 year.
Interested? Join @veronica and I as we go through the process together this Thursday Nov 6 at 2pm UTC / 5pm EAT / 7:30pm IST / 9am EST / 6am PST at om.rs/zoomgrace (after the o3 squad call).
About our Jira Graveyarding process: https://openmrs.atlassian.net/wiki/spaces/docs/pages/26272664/OpenMRS+Jira+Clean+Up+Protocol+aka+Quarterly+Graveyarding
Why:
To keep Jira up-to-date, many software organizations routinely bulk-close old issues that are older than a giver time period. This is helpful for us at OpenMRS because otherwise our backlog quickly becomes too huge and old to be helpful. Simply leaving tickets endlessly open can become unsafe, since the noise can obscure critical issues that still need addressing. This doesn’t mean we just throw out old ideas and bugs that are still useful: the process described here helps ensure that still relevant & important issues remain, and even those that are bulk-closed are not actually deleted. (Further details and history here.)
When:
~Quarterly. Our rough goal is to keep our average issue response time (time from reporting to closure) less than 1 year. We also only close issues that have not been updated in >1 year. For example, an issue created in 2003 that has been updated or worked on within the last 12 months would not be a Graveyard Candidate.