Deprecate JIRA Project HZN and move issues to NMS

The development of OpenNMS Horizon and Meridian is managed in JIRA in two projects HZN and NMS. The original nature of the HZN project allowed to use a more story driven workflow and the NMS project had more a bug driven workflow. Releases for new versions are driven by the NMS project and is also the source for our release notes.

To simplify our release process and also take the burden from our users to figure out in which project they have to create issues, we will Move all issues from HZN into the NMS project. Meanwhile we have adjusted the NMS project workflow in a way to support the same issue types as the HZN project.

While moving these JIRA issues, the link to the old HZN issue numbers will automatically be redirected to the new NMS issue number and we should not have broken links in our already created release notes.

I’ll break down the migration in several phases to avoid as much distortion from current development as possible. The HZN doesn’t have security levels so I will assign them in NMS with the security level “Default”.

We use these security levels for example when we get security related issues we don’t have a fix for them yet or when issues have sensitive data.

:white_check_mark: Phase 1: Move closed/resolved issues

:white_check_mark: (113) Step 1: Move Bugs from HZN to NMS, investigate all missing components create them in NMS so they can be reassigned.

:white_check_mark: (132) Step 2: Move Enhancements from HZN to NMS, investigate all missing components create them in NMS so they can be reassigned.

:white_check_mark: (35) Step 3: Move Epics and Configuration issues from HZN to NMS, investigate all missing components create them in NMS so they can be reassigned.

:white_check_mark: (41) Step 4: Move Tasks with Sub-Tasks, probably manual interaction required

:white_check_mark: (1) Step 5: Move Other issue types

:white_check_mark: (4) Step 6: Move New Feature

:white_check_mark: (589) Step 7: Move Stories

:white_check_mark: Phase 2: Move open issues not in a current sprint

:white_check_mark: (49) Step 1: Move Bugs from HZN to NMS, investigate all missing components create them in NMS so they can be reassigned.

:white_check_mark: (56) Step 2: Move Enhancements from HZN to NMS, investigate all missing components create them in NMS so they can be reassigned.

:white_check_mark: (53) Step 3: Move Epics and Configuration issues from HZN to NMS, investigate all missing components create them in NMS so they can be reassigned.

:white_check_mark: (29) Step 4: Move Tasks with Sub-Tasks, probably manual interaction required

:white_check_mark: (5) Step 5: Move New Feature

:white_check_mark: (156) Step 6: Move Stories

:white_check_mark: (2) Step 7: Move reopened issues

:white_check_mark: Phase 3: Move issues in review and work in progress

:white_check_mark: (5) Step 1: Move in review issues

:white_check_mark: (17) Step 1: Move in progress issues

:white_check_mark: Phase 4: Cleanup

:white_check_mark: Step 1: Delete HZN project and test redirects

:white_check_mark: Step 2: Set new issue number for outstanding PRs

1 Like

:tada: Project HZN is deleted and everything related to OpenNMS needs to go to the NMS project.

1 Like