nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't submit a release as date format is rejected by server

Colin Sauvanet_27pqfe

Hello Community,

I am using the default cloud Jira "new release" interface, on a Kanban project.

I am letting the default date format and it always gets rejected, it started at latest Monday 7th December (it was good on Monday 30th November)

I tried many format I could imagine but it's always getting rejected.

Did anyone experienced this issue ?

Thanks

Colin

Accepted answers

Colin Sauvanet_27pqfe

Looks like the issue is fixed in Jira Cloud now.

We can create releases as before.

All comments

Bill Sheboy

Hi @Colin Sauvanet

When you use the calendar picker to select the date, what format does it enter in the field?

Best regards,
Bill

Colin Sauvanet_27pqfe

Hi @Bill Sheboy

The date in the screenshot is the format output from the date picker.

14/Dec/20

I have tried many other formats including "2020-14-12" which seems to be the technical format.

We tried it from 2 different laptops (Ubuntu and MacOS) and from FireFox / Safari / Chrome.

Hint: we walked around the issue by creating manually a Release in the Release page and assigning manually tickets to it.

Best regards,

Colin

Bill Sheboy

Hi @Colin Sauvanet

I tried to create a version (Classic Board) using the same steps and it worked for me with that same date format. And, I saw some older resolved defects in the public backlog for this symptom fixed about 5 years ago.

I suggest asking your site admin to check your settings:

Administration > System > Look and Feel >Date/Time Formats

If that does not help, please ask your admin to submit a defect to Atlassian:

https://support.atlassian.com/contact/#/

Colin Sauvanet_27pqfe

Thanks @Bill Sheboy but we did not find anything in Admin Panel.

Configuration did not change recently.

We will try contacting support.

Colin Sauvanet_27pqfe

Workaround:

create a release manually (status will be "unreleased")
bulk edit all tickets that must go to that release
update fix version
- Change Fix versions
- Replace All With
- Chose version
confirm
Release manually (change status do "released")

Bill Sheboy

Hi @Colin Sauvanet

Do you have a way to programmagically determine which issues go in the version, such as a specific field in the issues? If so, you may be able to accomplish this using an automation rule.

Best regards,

Bill

Colin Sauvanet_27pqfe

Looks like the issue is fixed in Jira Cloud now.

We can create releases as before.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

board

kanban

date

release