NimsForest Issues

Migrate issues.experiencenet.com to issues.nimsforest.experiencenet.com
proposed improvement Priority: medium Project: nimsforestissue Reporter: 17 Mar 2026 11:48

Description

When nimsforest is switched on for the experiencenet organization, migrate the hydraissue instance at issues.experiencenet.com (78.47.174.83) to a nimsforestissue instance at issues.nimsforest.experiencenet.com on land.

This follows the same pattern as the nimsforest org migration: fork hydraissue → nimsforestissue, deploy as a land container, migrate existing issues, and decommission the old instance.

Blocked until: nimsforest ecosystem is enabled for the experiencenet organization.

Comments (1)

nebula 17 Mar 2026 12:01
Grooming: set priority to medium

Nebula's reasoning: This is a well-documented migration task with a clear blocker (nimsforest ecosystem must be enabled for the experiencenet org first). Medium priority is appropriate — it's an important infrastructure consolidation but not urgent since it's explicitly blocked on an external dependency. Category, project, title, and description are all already clear and accurate.