/
Abandoned Issue Policy

Abandoned Issue Policy

Sometimes contributors pick up a Jira ticket with good intentions, and then may not be able to continue working on that ticket. Life gets busy - we understand! In order to keep issues available for other contributors, and to ensure work is not blocked, we follow these principles:

  • No Shame: There is no shame in unassigning yourself from an issue you picked up and realize you cannot continue. It is better to unassign yourself than to leave others waiting and wondering what is happening.

  • Ask for Updates: If there are no updates on an issue within the last week or more, you can ask the Assignee for an update on the issue, and ask if you or others could help or pick it up instead.

  • Sometimes Things get Urgent: Issues can be immediately marked “Unassigned” or reassigned in these cases:

    • If no updates in >1 month (in ticket comments); or,

    • If no updates in >1 week or no updates provided at all, and the issue is critical for a member organization’s production implementation, this can be reassigned immediately.

Related content

OpenMRS Jira Clean Up Protocol (aka "Quarterly Graveyarding")
OpenMRS Jira Clean Up Protocol (aka "Quarterly Graveyarding")
More like this
Community priority tickets for the Platform team
Community priority tickets for the Platform team
More like this
Release Prioritization Meeting
Release Prioritization Meeting
More like this
Pull Request Tips
Pull Request Tips
More like this
How to access issues
How to access issues
More like this
Working on OpenMRS Platform 1.11 Release Test Failed Tickets
Working on OpenMRS Platform 1.11 Release Test Failed Tickets
More like this