After restoring Jira Cloud backup to Jira Data Center, Plans are Inaccessible

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

After restoring Jira Cloud backup to Jira Data Center, Plans are Inaccessible to users. Users can click on "plans" > "All Plans" from the top navigation menu, but no plans (or some of those) are actually visible, and therefore, they are inaccessible.

Environment

9.12.2 - 9.15.0

Diagnosis

In the atlassian-jira.log file, you will see an error occur like this:

1 2 http-nio-8080-exec-5 url: /jira/rest/jpo/1.0/programs/list; ERROR /rest/jpo/1.0/programs/list [c.a.r.j.c.plan.sql.QueryDslPlanPersistence] Invalid plan stored with ID 76 2024-01-11 19:55:55,071+0000 http-nio-8080-exec-5 url: /jira/rest/jpo/1.0/programs/list; ERROR /rest/jpo/1.0/programs/list [c.a.r.j.c.plan.sql.QueryDslPlanPersistence] number must be positive: Optional.of(0)

Cause

The Plans that were included in the backup from Jira Cloud contain incompatible values within Jira Data Center's database.

Solution

To fix this, you can stop Jira and then run the following queries in Jira's database.

⚠️ Always backup your database prior to running these Database Queries

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 update "AO_D9132D_PLAN" set "GLOBAL_DEFAULT_VELOCITY" = NULL where "GLOBAL_DEFAULT_VELOCITY" = 0; update "AO_D9132D_PLAN" set "MAX_RESOURCES_PER_STORY" = NULL where "MAX_RESOURCES_PER_STORY" = 0; update "AO_D9132D_PLAN" set "MIN_LOAD_UNSTR_EPICS" = NULL where "MIN_LOAD_UNSTR_EPICS" = 0; update "AO_D9132D_PLAN" set "HOURS_PER_DAY" = NULL where "HOURS_PER_DAY" = 0; update "AO_D9132D_PLAN" set "GLOBAL_SPRINT_LENGTH" = NULL where "GLOBAL_SPRINT_LENGTH" = 0; UPDATE "AO_D9132D_PLAN" set "PLANNING_UNIT" = 0 where "PLANNING_UNIT" IS NULL; UPDATE "AO_D9132D_PLAN" SET "ISSUE_INFERRED_DATE_SELECTION" = NULL WHERE "ISSUE_INFERRED_DATE_SELECTION" = 2;
Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.