IT recently updated from 9.12.18 to 10.3 and in the process broke the Advanced Roadmap pages. Prior to the upgrade, we could select a date field and key in the date via the keyboard (e.g., 1/11/26). Now, that no longer works.
Steps:
1. Open up any advanced roadmap and select a date field to edit
2. The date picker calendar displays
3. Rather than selected a displayed date, key in the date, such as 1/11/2031. Keyboard entry previously worked.
4. Now, keyboard entry does not work, so, to pick 1-Jan-2031 now requires selecting the next month 61 times!
I cannot believe this is intended change, but our IT does not have a solution beyond saying to stop using advanced roadmaps.
Does anyone have a solution?
This is a known regression in Advanced Roadmaps for Jira Data Center 10.x. The date picker component was updated to the new Atlassian UI library, which currently blocks direct text input in date fields. Atlassian confirmed this behavior change in recent Jira Data Center release notes and internal bug reports. Keyboard entry was supported in 9.x but replaced by a strict calendar-only picker in 10.3.
There isn’t a configuration toggle to restore typing dates.
That's inconvenient to say the least if your dates are more than a few months from the current month and year.
My project spans through 2034 and the date picker is a real problem. Until (hopefully) they fix this, is it possible to remove the date picker entirely and use simple keyboard date entry?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is worse than you describe, OP.
Who at Atlassian thinks people don't use a keyboard and mouse to enter information into a form?
C'MON!!! This is ridiculous!
As OP states, any time the desired date is not within the current calendar month, the date picker makes it less efficient (I call it useless). Do you do ANY testing to simulate high-volume users or do you simply run one test assuming users need only select 1 date per day????
When story grooming or sprint planning and modifying many stories, this inefficiency compounds. I dread sprint planning because I know it will be a time-killer of inefficient clicking and left/right scrolling in the sub-task tables.
If you're going to jam the date picker on the user, at least put some controls on it to move forward/backward a year or a drop-down to select a month.
Don't get me started on changing the status of a sub-task and then being flung back to the top of the page, so I have to scroll back down to the sub-task table.
BETTER YET - LET ME USE THE KEYBOARD TO TYPE IN A DATE AND HIT ENTER!!!!
FRUSRATED!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.