Portfolio fails to save auto schedule changes
Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.
Problem
After creating a Portfolio live plan clicking on "Auto Schedule" at the upper right corner and by 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 vshanmugam 472x4707x1 g0ptpb 10.95.89.43,192.168.128.32 /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 filteredCause
The problem happens because some function related to the simple plan is disabled.
Resolution
- Access <Jira_URL>/secure/SiteDarkFeatures!default.jspa URL.
- If you find the *com.atlassian.portfolio.simpleplans.disabled* package, remove it.
- After removing it, check if you are able to commit.
Last modified on May 30, 2019
Powered by Confluence and Scroll Viewport.