I wanted to share information that relates to our ticket tracker, Jira.
- You may get notice that an issue you are watching has been closed with a resolution of “obsolete”.
- If you find this action to be by mistake, follow the instructions in the comment that was attached to the ticket.
- More information related to when we migrate from Jira Server to Jira Cloud will be announced.
- We will attempt to migrate everything: user accounts and tickets will be as they were.
- Jira Cloud has an updated user interface, so it will look and feel more modern.
The Jira Software product that we use at jira.dhis2.org is nearing its end-of-life, and what that means for us is that we have started thinking about what to do when that happens.
We would like to keep using Jira, but not necessarily spend resources hosting it ourselves as we have done in the past, and Atlassian has offered us to move to Jira Cloud instead.
In preparation, we are in the process of cleaning up Jira to make it easier to work with.
Our Jira has gathered a lot of cruft over the years, both in terms of configuration and stale tickets, and we need to do a round of significant cleanups to improve the health of Jira as a tool for everyone.
The clean up happens on two sides, one is the configuration side to make it easier to manage over time, and the second is to close issues that are no longer applicable to supported versions of DHIS2.
When we cannot determine if an issue is still relevant, we will close it with the resolution “Obsolete” and add a comment about possible actions you can take if you think that the issue was closed by mistake to get it re-opened and re-prioritized.
- DHIS2 Jira: Filter that shows all the issues marked as stale
- Atlassian: Jira Server end-of-life timeline
We are sorry about the inconvenience this causes you and that you are happy with the end results !