Advanced Roadmaps for Jira New Jira issues created in a plan can not be saved or committed

Summary

The purpose of this KB article is to list all the known scenarios where a user is unable to save a Jira issue created in a Plan by using the Review Changes functionality. This KB article will address the following symptoms:

• The Set Required Fields screen pops up after clicking on the Save selected changes in Jira button, but nothing happens when clicking on the Create button

  

• The Set Required Fields screen pops up after clicking on the Save selected changes in Jira button, but the error "There is 1 error in this form" is shown when clicking on the Create button:

  

• When clicking on the button Save selected changes in Jira, the action fails and the error "Changes couldn't be saved" pops up at the bottom left of the screen:

  

• When clicking on the button Save selected changes in Jira, Jira hangs in the 'Saving in Jira...' progress screen:

  

Environment

Jira Software on Server/Data Center on any version from 8.15.0.

Diagnosis

Diagnosis for Root Cause 1

To check if this root cause is relevant, follow the steps below:

• When clicking on the Create button from the Set Required Fields screen, nothing happens:

  

• The Set Required Fields screen is not showing the same list of mandatory fields as in the regular Create Issue screen:

  • In the Set Required Fields screen, one of the mandatory field is missing (the Fix Version field in the example below):

    

  • The Create Issue screen is showing more mandatory fields (in the example below, the Fix Version field is showing because it is required):

    

• There are at least 2 mandatory fields showing in the Create Issue screen, and:

  • One of them is set to Mandatory via Jira's native Field Configuration

  • The other field is set as a Mandatory field in the behaviors configuration of the ScriptRunner For Jira add-on, as illustrated below:

    

Diagnosis for Root Cause 2

• The Set Required Fields screen pops up after clicking on the Save selected changes in Jira button, but the error "There is 1 error in this form" is shown when clicking on the Create button:

  

• There is a Fields Required validator that is associated to the Create transition in the workflow used by the newly created issue

  • This validator is not coming from the JSU Automation Suite for Jira Workflows add-on

  • Instead, this validator is coming from a different add-on, for example (the list of examples below is not exhaustive)

    • ScriptRunner For Jira

      

    • Jira Misc Workflow Extensions (JMWE)

      

Diagnosis for Root Cause 3

• When clicking on the button Save selected changes in Jira, the action fails and the error "Changes couldn't be saved" pops up at the bottom left of the screen

  

• The Jira application is on any of the versions below

  • Any version below 9.12.19

  • Any version 9.13.x, 9.14.x, 9.15.x, 9.16.x

  • Any 9.17.x version below 9.17.5

  • Any Jira 10.x version below 10.2.0

• There is a Fields Required (JSU) validator (coming from the JSU Automation Suite for Jira Workflows add-on) that is associated to the Create transition in the workflow used by the newly created issue:

  

Diagnosis for Root Cause 4

• When clicking on the button Save selected changes in Jira, Jira hangs in the 'Saving in Jira...' progress screen:

  

• When opening the Browser Network Tool, we can see that a call is made to an end point from the JSU 3rd party add-on (even if this add-on is not installed in the Jira application), that returns with a 404 error:

  1 /rest/jsu/1/workflow/fieldsrequired/create/10101/10100

• The error below is found in the Jira logs:

  1 2 3 4 2025-04-09 09:29:04,443+0000 http-nio-8080-exec-33 url: /jsm/rest/jpo/1.0/issues/commit; user: admin WARN admin 569x1228x1 xsj1es XXXXXX /rest/jpo/1.0/issues/commit [c.a.r.j.c.scenario.common.BaseScenarioEntityCommitService] Error in commit operation. com.atlassian.rm.jpo.env.issues.IssueRequiredFieldsMissingException: Required Fields not set. [description] at com.atlassian.rm.jpo.env.issues.JiraIssueValidationService.validate(JiraIssueValidationService.java:90)

• The warning below is found in the Jira logs, after the error below:

  1 2025-04-09 09:29:04,446+0000 http-nio-8080-exec-33 url: /jsm/rest/jpo/1.0/issues/commit; user: admin WARN admin 569x1228x1 xsj1es XXXXXXXX /rest/jpo/1.0/issues/commit [c.a.r.j.c.scenario.issue.IssueScenarioEntityCommitExceptionHandler] Exception when trying to commit issue: Required Fields not set. [description].

• The Jira application is on any of the versions listed below:

  • Any Jira 9.12.x version from 9.12.19

  • Any Jira 9.17.x version from 9.17.5

Diagnosis for Root Cause 5

• On the Review Changes area when attempting to commit changes, you may see "Not in plan" for the priority field:

• When clicking on the button Save selected changes in Jira, the action fails and the error "Changes couldn't be saved" pops up at the bottom left of the screen

  

• The error below is found in the Jira logs:

  1 2 3 4 5 6 7 8 9 10 11 2021-08-05 22:07:53,602-0700 https-jsse-nio-443-exec-35 url: /rest/jpo/1.0/issues/commit; user: useruser WARN useruser 1327x970117x1 y11kfi 10.21.16.102 /rest/jpo/1.0/issues/commit [c.a.r.j.env.issues.JiraIssueService] Could not create issue. Validation-errors: {priority=The priority selected is invalid.} 2021-08-05 22:07:53,603-0700 https-jsse-nio-443-exec-35 url: /rest/jpo/1.0/issues/commit; user: useruser WARN useruser 1327x970117x1 y11kfi 10.21.16.102 /rest/jpo/1.0/issues/commit [c.a.r.j.c.scenario.common.BaseScenarioEntityCommitService] Error in commit operation. com.atlassian.rm.jpo.env.issues.EnvironmentIssueCreateException: Specific error details: {priority=The priority selected is invalid.} at com.atlassian.rm.jpo.env.issues.JiraIssueService.createIssue(JiraIssueService.java:728) at com.atlassian.rm.jpo.env.issues.JiraIssueService.createIssue(JiraIssueService.java:164) at com.atlassian.rm.jpo.core.scenario.issue.ScenarioIssueCreateAction.performApiOperation(ScenarioIssueCreateAction.java:88) at com.atlassian.rm.jpo.core.scenario.issue.ScenarioIssueModificationAction.perform(ScenarioIssueModificationAction.java:317) at com.atlassian.rm.common.persistence.transaction.Registry.run(Registry.java:35) at com.atlassian.rm.jpo.core.scenario.issue.ScenarioIssueCommitService.add(ScenarioIssueCommitService.java:137) at com.atlassian.rm.jpo.core.scenario.issue.ScenarioIssueCommitService.add(ScenarioIssueCommitService.java:47) at com.atlassian.rm.jpo.core.scenario.common.BaseScenarioEntityCommitService.addInternal(BaseScenarioEntityCommitService.java:349)

Cause

Root Cause 1

One of the field is configured as mandatory via the behaviors configuration of the ScriptRunner For Jira add-on, which is not supported by Advanced Roadmaps plans. Because of this limitation, this mandatory field is not showing in the Set Required Fields screen and as a result, the Jira application fails to create the issue since this field is mandatory but cannot be set via the UI.

This limitation is tracked in the feature request JSWSERVER-26125 - The "Set Required Field" screen does not take into account mandatory fields from ScriptRunner behaviors.

Root Cause 2

There is a Fields Required validator that is associated to the Create transition in the workflow used by the newly created issue, which is:

• not coming from the JSU Automation Suite for Jira Workflows add-on

• coming from a different add-on, for example (the list of examples below is not exhaustive)

  • ScriptRunner For Jira

  • Jira Misc Workflow Extensions (JMWE)

Such configuration is not supported by Advanced Roadmaps plans. Because of this limitation, this mandatory field is not showing in the Set Required Fields screen and as a result, the Jira application fails to create the issue since this field is mandatory but cannot be set via the UI.

Root Cause 3

The issue type is associated to a workflow that is using the "required field" validator in the 'create' transition, that is coming from the JSU Automation Suite for Jira Workflows add-on. In older Jira versions, the required fields configured by this add-on validator were not showing in the Set Required Fields screen and as a result, the Jira application would fail to create the issue since this field is mandatory but cannot be set via the UI.

This behavior was tracked in the bug ticket JSWSERVER-24900 - Issue Creation fails within the plan if workflow validators from the JSU add-on are used.

This bug was fixed in the versions 9.12.19, 9.17.5, 10.2.0.

Root Cause 4

We are facing the bug JSWSERVER-26255 - Set Required Fields screen does not show and the screen freezes when committing changes to Advanced Roadmaps Plans, which impacts:

• Any Jira 9.12.x version from 9.12.19

• Any Jira 9.17.x version from 9.17.5

ℹ️ Note that this bug does not impact Jira versions from 10.0.0.

Root Cause 5

There is some issue with the Priority Scheme associated to the project the newly created issue belongs to. While the exact root cause is actually unclear, you may refer to the KB article linked below to get more information about what we know about this root cause, and how to address it:

Unable to commit creation of new issue from Advanced Roadmaps Plans due to the Priority Scheme configuration

Solution

Solution for Root Cause 1

Workaround 1

Instead of using ScriptRunner behaviors to make the field mandatory, make it mandatory via Jira's native Field Configuration as illustrated below:

Workaround 2

If using Jira's native Field Configuration to make a feed required is not possible (for example, it is not possible to make the Parent Link field required because it's a locked field), and you need to use ScriptRunner's behaviors instead, try this workaround.

This workaround consists in adding to the announcement banner the script mentioned in the feature request JSWSERVER-26125. This script will automatically include all the fields to the Set Required Fields screen, including the the field set as required through the ScriptRunner behavior configuration.

Solution for Root Cause 2

For this root cause, the good news is that, after the error "There is 1 error in this form" is thrown in the UI, the field set as required should appear in the Set Required Fields screen (while it was not appearing at first).

Therefore, it will be possible for the Jira user to fill in the required field in the Set Required Fields screen.

Note that there is currently no long term solution nor better workaround, since the Set Required Fields screen from Advanced Roadmaps For Jira does not support well 3rd party add-ons.

Solution for Root Cause 3

Workaround 1

Upgrade the Jira application to a fixed version:

• Any Jira 9.12.x version from 9.12.19

• Any Jira 9.17.x version from 9.17.5

• Any Jira version from 10.2.0

Workaround 2

If upgrading is not an option yet, instead of using JSU workflow validator to make the field required, make it required via Jira's native Field Configuration as illustrated below:

Solution for Root Cause 4

Workaround 1

Upgrade the Jira application to any version from 10.0.0.

Workaround 2

If upgrading the Jira application is not an option yet, you may use this workaround instead.

This workaround consists in enabling the dark featurecom.atlassian.portfolio.issueCreation.ShowWorkFlowValidatorFields.disabled by following the steps below:

• Login as a System Jira Administrator

• Go to the URL below

  1 <BASE_URL>/secure/admin/SiteDarkFeatures!default.jspa

• Add the flag below to the Enable dark feature field and click Add

  1 com.atlassian.portfolio.issueCreation.ShowWorkFlowValidatorFields.disabled

Solution for Root Cause 5

Please refer to the Solution section of the KB article Unable to commit creation of new issue from Advanced Roadmaps Plans due to the Priority Scheme configuration.