Issues / #1
Migrate issues.experiencenet.com to issues.nimsforest.experiencenet.com
accepted
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.
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 (3)
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.
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.
nebula
18 Mar 2026 11:02
Plan review: rejected — High risk with unmet prerequisite
Nebula's reasoning: This involves production data migration, DNS changes, and service cutover. The plan itself notes it is blocked until the nimsforest ecosystem is enabled for ExperienceNet. Needs human coordination for the migration and cutover timing.
Nebula's reasoning: This involves production data migration, DNS changes, and service cutover. The plan itself notes it is blocked until the nimsforest ecosystem is enabled for ExperienceNet. Needs human coordination for the migration and cutover timing.
nebula
18 Mar 2026 11:17
Plan review: accepted
Nebula's reasoning: The revised plan creates only preparation artifacts — config templates, a land.yaml snippet, and a migration runbook. No production data migration, DNS changes, or service cutover. The blocked dependency is acknowledged and the preparation work is safe to proceed independently.
Nebula's reasoning: The revised plan creates only preparation artifacts — config templates, a land.yaml snippet, and a migration runbook. No production data migration, DNS changes, or service cutover. The blocked dependency is acknowledged and the preparation work is safe to proceed independently.