Can't create new issues directly from Plans (Advanced Roadmaps)

[Boeing_ Nick]

We are having trouble creating new issues directly from plans.  We'll create a draft issue on the plan, schedule it and add detail (such as start dates, due dates, dependencies, child issues). 

We then open up "Unsaved Changes" and save the new issue.  We then get an error message that says "Couldn't save changes", with a prompt that asks us to "Open Unsaved Changes". 

When we open up this prompt we get taken to the "Create Issue" screen where it says that that required fields must be added.  However all required fields are filled in from Plans, and we can simply hit "Create" from this screen without making any modifications to the data. 

We've checked that the users who are creating issues have the correct permissions, and we've also checked to see if there are any validators on the workflow for creating an issue and confirmed that there are no hidden validators.  

[Trudy Claspill · Accepted solution]

Hello @Boeing_ Nick 

Welcome to the Atlassian community.

When you say that all the Required fields are filled from Plans do you mean all the fields shown in the Create dialog that have a red asterisk?

Have you clicked the ... button in the upper right corner of the create dialog and clicked the options to ensure all fields are being shown in the dialog?

If this is for a Company-managed project, have you checked the Field Configuration associated with the issue type in that project to see if there are other fields marked as Required that are not showing in the Create dialog?

[Trudy Claspill]

I reread your post and I see that you said that from the Create issue dialog you can hit Create and the issue creates without any additional input from the user.

In that case I would still click the ... button and make sure all fields are revealed, and double check that the ones with asterisks match the ones filled in within the Plans screen.

Do you perhaps have any third party app that is filling fields based on values from other fields, such as the ScriptRunner Behaviours app or the Appfire Live Fields app?

Do you have a required field that is not being set in Plans but gets a default value per the custom field configuration?

[Boeing_ Nick]

This worked, we had another required field in our configuration that was blocking us from creating the issue from the Plan view.  Once I put in a value for the field I was able to create the issue from Plans

[Oleksii Melnyk _MOY Apps_ · Accepted solution]

Hi @Boeing_ Nick !

This issue is usually caused by a mismatch between your Space (Project) Field Configuration and the columns visible in your Plan.

The most likely culprit: You have a field marked as Required in your Field Configuration, but that field is not added as a column in your Plan view. When you try to save, the Plan cannot send data for that missing field, causing the API to fail. Once the "Create Issue" modal opens, it re-validates the fields correctly, which is why it lets you click "Create" without further changes.

Can you double-check that you can create absolutely the same work item with the create button as you are trying to create with Plans?

[Boeing_ Nick]

This worked, there was one custom field required on our default field configuration.  Once we added it to the plan, and put a value in I was able to create the issue without having to go through the "Create Issue" dialogue.  Thanks!