Portfolio plan fails to save auto schedule changes

Still need help?

The Atlassian Community is here for you.

Ask the community


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

After creating an Advanced Roadmap for Jira live plan by clicking on "Auto Schedule" at the upper right corner and clicking "Accept Changes", there was an error shown, and the changes are not committed to Jira.

The following appears in the atlassian-jira.log when the failure happened:

2019-05-22 07:52:36,229 http-nio-8080-exec-7 ERROR xxxxxx xxxx xxx xxx /rest/jpo/1.0/scheduling/commit [c.a.r.c.r.provider.exception.DefaultExceptionMapper] 
com.atlassian.rm.jpo.env.features.FeatureNotEnabledException
	at com.atlassian.rm.jpo.core.scheduling.commit.DefaultCalculationCommitService.commitAsync(DefaultCalculationCommitService.java:47)
	at com.atlassian.rm.jpo.rest.service.scheduling.commit.SchedulingCommitRestEndpoint.startCommitJob(SchedulingCommitRestEndpoint.java:73)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	... 8 filtered

Cause

The problem happens because some function related to the simple plan is disabled.

Resolution

  1. Access <Jira_URL>/secure/SiteDarkFeatures!default.jspa URL.
  2. If you find the com.atlassian.portfolio.simpleplans.disabled package, remove it.
  3. After removing it, check if you are able to commit.


Last modified on Sep 29, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.