Unable to commit the item baselineStart in the Review Changes
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
In Plans, the review changes cannot be saved:
Environment
- Jira DC 9.4.0
Diagnosis
In the application-jira.log, you will get NullPointerException to retrieve the Target dates field value:
2023-01-12 14:06:22,633+0100 http-nio-8080-exec-7 WARN xxxx 846x1382x1 zxxzx /rest/jpo/1.0/issues/commit [c.a.r.j.c.scenario.issue.ScenarioIssueModificationAc
tion] Target dates could not be set.
java.lang.NullPointerException
at com.atlassian.rm.jpo.core.scenario.issue.DefaultScenarioIssueBaselineDatesAction.setBaselineStart(DefaultScenarioIssueBaselineDatesAction.java:98)
at com.atlassian.rm.jpo.core.scenario.issue.DefaultScenarioIssueBaselineDatesAction.setBaselineDates(DefaultScenarioIssueBaselineDatesAction.java:66)
at com.atlassian.rm.jpo.core.scenario.issue.ScenarioIssueModificationAction.perform(ScenarioIssueModificationAction.java:361)Validate if you are affected by the KB Indexing breaks after upgrading to Advanced Roadmaps to Jira 3.29.2 when Team field was renamed or is missing
Before proceeding with the solution in the KB, please run the following SQL query via database to check the missing fields:
SELECT * FROM customfield WHERE customfieldtypekey LIKE 'com.atlassian.jpo%'; Cause
The following Advanced Roadmaps system fields went missing via Custom Field page:
- Team
- Target date
- End date
Solution
- Follow the solution suggested in the KB article to create the missing field.
- Don't lock the field yet.
- Change the Team field to Global context via the Custom Field page.
- Commit the unsaved changes of the plan.
- Lock the field after able to commit the changes.