Changes made in Advanced Roadmaps plan are not reflected in Jira although success message is seen.

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

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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

Changes made to Jira issue fields from Advanced Roadmaps plan are not reflected on the Jira issue, although you can see the message "change was successfully saved to Jira" after using the "Review Changes" functionality:


Environment

Jira Server/Data Center 8.20.0 and any higher version

Diagnosis

While saving the changes, following message is logged in the application log (atlassian-jira.log). Notice, the line that says feature disabled in feature manager

2024-05-31T06:40:19.914Z | https-jsse-nio-8443-exec-11 url: /rest/jpo/1.0/issues/commit; user: XXX | DEBUG | [XXX] | [520x322067x1] | [2mdj5] | [XXX,XXX] | [/rest/jpo/1.0/issues/commit] | [c.a.r.j.c.scenario.issue.DefaultScenarioIssueAssigneeAction] | set issue assignee for issue: 799281
2024-05-31T06:40:19.914Z | https-jsse-nio-8443-exec-11 url: /rest/jpo/1.0/issues/commit; user: XXX | DEBUG | [XXX] | [520x322067x1] | [2mdj5] | [XXX,XXX] | [/rest/jpo/1.0/issues/commit] | [c.a.r.j.c.scenario.issue.DefaultScenarioIssueAssigneeAction] | try to get assigneeId for given resources Optional.absent()
2024-05-31T06:40:19.914Z | https-jsse-nio-8443-exec-11 url: /rest/jpo/1.0/issues/commit; user: XXX | DEBUG | [XXX] | [520x322067x1] | [2mdj5] | [XXX,XXX] | [/rest/jpo/1.0/issues/commit] | [c.a.r.c.env.features.JiraFeatureTester] | test feature: SIMPLE_PLANS
2024-05-31T06:40:19.914Z | https-jsse-nio-8443-exec-11 url: /rest/jpo/1.0/issues/commit; user: XXX | DEBUG | [XXX] | [520x322067x1] | [2mdj5] | [XXX,XXX] | [/rest/jpo/1.0/issues/commit] | [c.a.r.c.env.features.JiraFeatureTester] | try to read feature from feature manager
2024-05-31T06:40:19.914Z | https-jsse-nio-8443-exec-11 url: /rest/jpo/1.0/issues/commit; user: XXX | DEBUG | [XXX] | [520x322067x1] | [2mdj5] | [XXX,XXX] | [/rest/jpo/1.0/issues/commit] | [c.a.r.c.env.features.JiraFeatureTester] | feature disabled in feature manager 

Check the dark features for the site by accessing <BASE_URL> /SiteDarkFeatures!Default.jspa as Jira Admin and verify if com.atlassian.portfolio.simpleplans.disabled is set as shown below.

Cause

com.atlassian.portfolio.simpleplans.disabled Dark Feature is preventing the changes to be saved to Jira.

Solution

Disable the Dark Feature com.atlassian.portfolio.simpleplans.disabled (by following the instructions in the dark features documentation) and retry saving the changes: the changes should now be reflected in the Jira issue view.

Last modified on Jan 24, 2025

Was this helpful?

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