Issue Summary

Whenever a user is creating an issue, if setting 2099 for year value in a date picker field, 1999 value is stored instead.

Steps to Reproduce

1. Create a new issue setting date picker field using 2099 as year
2. It's possible to set this value, but Jira automatically updates this to 1999, which is the value shown in issue view

Expected Results

The 2099 should be kept and stored.

Actual Results

Although the correct date seems to be sent in payload in frontend, 1999 is stored as value in backend:

"customfield_10056": "1999-01-09", 

Workaround

After the issue is created, it's possible to update year data from 1999 to 2099. The bug only affects issue creation.