Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

ISSUE: This form contains a hidden field that does not have a valid default value configured


We have a very simple form used for our onboarding/termination process. This form was working fine until a few days ago and now we are receiving the following error when trying to send/submit the form.

We've checked the form under Request Types and there are no hidden fields assigned.

Has anyone run into this issue? Can anyone offer any ideas?


3 answers

I know this is an old thread but it came up during my search trying to figure out what was wrong in 2021.


For anyone that is running into this issue you may try seeing if it has anything to do with your Sprints. I have a lot of different classic projects and service desk projects that I manage and I just ran into this error for the first time. 


For me, I had to check the Network tab and find the 400 error since we are on Jira Cloud and I don't have a log to look at. Once I did I was able to preview the error and it was talking about an error with the Sprint. I knew the Sprint existed as other projects have used it plenty of times. 


Screen Shot 2021-11-16 at 7.00.48 PM.png


However, after testing this a bit more it was due to not ever having used that specific Sprint within that Support portal. So I went to the backlog where I knew the sprint was and added a single ticket from that project to that Sprint temporarily and then moved it back to its original Sprint which resolved the issue.


Hopefully, this helps someone.

@Steve Martinez  Check if you are using dynamic forms which is an extension to Jira servicedesk, We ran into this issue once where one of our mandatory fields was set as a dynamic field value and was not appearing on form even if we put it in Request types,

0 votes
Benjamin Community Leader Jul 21, 2021

Hi @Steve Martinez ,


I am assuming the error is in the title of this post. Usually, the error leads to the hidden fields that is auto-assigning a conflicting value.


I would try to recreate the form the same way and see if you have any issues with the new form. If not, just delete the one previous and use the new one. If you still have issues, then there be some change in the core project configuration other then the request types.


Help this helps.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

319 views 0 10
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you