Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-75894

Invalid format error when building and releasing a version

XMLWordPrintable

    • 9.07
    • 84
    • Severity 3 - Minor
    • 535
    • Hide
      Atlassian Update – 11 June 2024

      Dear Customers,
      Thank you for reporting this issue. In the last weeks we have been working on fixing it.

      Summary of the problem:

      The problem stemmed from the recent modification made for JRASERVER-41646. The issue came to light when it was discovered that the scheduled job responsible for releasing the version was internally utilizing an invalid data format.

      New behaviour after the change:

      Moving forward, the internal job will now schedule new 'Release' and 'Build and Release' jobs using the correct data format. This adjustment ensures that any newly triggered operations should be completed successfully.

      In cases where unfinished jobs were triggered by 'Build and Release' with an invalid data format before the upgrade to the fixed version, they may still be in progress. To address this issue, simply trigger the 'Release' operation once more.

      Best regards
      Daniel Dudziak
      Principal Software Engineer

      Show
      Atlassian Update – 11 June 2024 Dear Customers, Thank you for reporting this issue. In the last weeks we have been working on fixing it. Summary of the problem: The problem stemmed from the recent modification made for JRASERVER-41646 . The issue came to light when it was discovered that the scheduled job responsible for releasing the version was internally utilizing an invalid data format. New behaviour after the change: Moving forward, the internal job will now schedule new 'Release' and 'Build and Release' jobs using the correct data format. This adjustment ensures that any newly triggered operations should be completed successfully. In cases where unfinished jobs were triggered by 'Build and Release' with an invalid data format before the upgrade to the fixed version, they may still be in progress . To address this issue, simply trigger the ' Release ' operation once more. Best regards Daniel Dudziak Principal Software Engineer

      Issue Summary

      The error "Invalid format" is shown in the atlassian-jira.log when building and releasing versions.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. In JIRA Admin > System > Look and Feel set the Day/Month/Year Format to a format using spaces, e.g. 'dd.MMM.yy' (or any other date time format that is not the default)
      2. Go to the Versions list of any projects, and click Release for a Version; You will see it released without problems
      3. Then click Unrelease for the same version
      4. Now click Build and Release, and the screen refreshes multiple times falling into a loop.
      5. Return to the Versions lists and you will see the Version still is unreleased

      Expected Results

      The Version should be released regardless of the format configured in Look and Feel

      Actual Results

      The Version remains Unreleased and the Version page enters into a loop.

      The below example exception is thrown in the atlassian-jira.log file:

      http-nio-8080-exec-XXX url: /jira/rest/bamboo/1.0/status/10002/SCRUM-SP-X; user: USER ERROR USER XXXXX SESSIONID IP_ORIG /rest/bamboo/1.0/status/10002/SCRUM-SP-5 [c.a.j.p.e.bamboo.service.BambooReleaseServiceImpl] Unexpected Error Has Occured Performing Release
java.lang.IllegalArgumentException: Invalid format: "14.Jun.23" is malformed at ".Jun.23"
	at org.joda.time.format.DateTimeFormatter.parseLocalDateTime(DateTimeFormatter.java:900)
	at com.atlassian.jira.datetime.JodaDateTimeFormatter.parse(JodaDateTimeFormatter.java:42)
	at com.atlassian.jira.datetime.DateTimeDatePickerFormatter.parse(DateTimeDatePickerFormatter.java:28)
	at com.atlassian.jira.datetime.DateTimeFormatterImpl.parse(DateTimeFormatterImpl.java:51)
	at com.atlassian.jira.util.DateFieldFormatImpl.parseDatePicker(DateFieldFormatImpl.java:42)
	at jdk.internal.reflect.GeneratedMethodAccessor1139.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)

      Workaround

      1. Go to JIRA Admin > System > Look and Feel
      2. Revert the Day/Month/Year Format to the default format settings: dd/MMM/yy

      Or, release the version manually from the project's administration page for version.

      Notes

      There seem to be correlation with the Jira Admin > System > General Configuration > Advanced Settings > jira.date.picker.java.format. If reverting the values in 'Look and Feel' doesn't work, check the jira.date.picker.java.format value and sync it with the value in 'Look and Feel'

            [JRASERVER-75894] Invalid format error when building and releasing a version

            Barış Türkkal added a comment -

            https://getsupport.atlassian.com/browse/PS-173754

            Barış Türkkal added a comment - https://getsupport.atlassian.com/browse/PS-173754

            Cynthia Ayers added a comment -

            Is this bug fixed in the latest LTS version 9.12.x?

            Cynthia Ayers added a comment - Is this bug fixed in the latest LTS version 9.12.x?

            Hannes Medwed added a comment -

            Jira 9.12.11 DC was released on 4th of  July  but there is no indication if this bug is fixed. Since we have to update Jira in the next few days due to a vulnerability, it would be annoying if the problem still existed in this version.

            Hannes Medwed added a comment - Jira 9.12.11 DC was released on 4th of  July  but there is no indication if this bug is fixed. Since we have to update Jira in the next few days due to a vulnerability, it would be annoying if the problem still existed in this version.

            Zachariah Jones added a comment -

            We are also experiencing this issue on our instance of Data Center and we don't have a fix for it in the 9.12 branch, as mentioned in the comments the workaround solution selects the incorrect date in the datepicker, please provide a resolution for this bug ASAP.

            Zachariah Jones added a comment - We are also experiencing this issue on our instance of Data Center and we don't have a fix for it in the 9.12 branch, as mentioned in the comments the workaround solution selects the incorrect date in the datepicker, please provide a resolution for this bug ASAP.

            Jürgen Biersack added a comment -

            version 9.12.8 is also affected by this issue

            Jürgen Biersack added a comment - version 9.12.8 is also affected by this issue

            williamsray added a comment - - edited

            We only receive the error from the Release Detail page and not the Release List page.  We found that there is a second workaround that doesn't require reverting you display formats.  There is a "Release" option that appears beneath the [...] context menu from the "Releases" view of the Project.  This option prompts for the Release Date and does not throw an error message when selected.  We still use the Release Details page for creating release notes, but release using the context menu.

            williamsray added a comment - - edited We only receive the error from the Release Detail page and not the Release List page.  We found that there is a second workaround that doesn't require reverting you display formats.  There is a "Release" option that appears beneath the [...] context menu from the "Releases" view of the Project.  This option prompts for the Release Date and does not throw an error message when selected.  We still use the Release Details page for creating release notes, but release using the context menu.

            Rafał Falisz added a comment -

            Version 9.12.7 is also affected. 

            Rafał Falisz added a comment - Version 9.12.7 is also affected. 

            Martin E added a comment - - edited

            and what happens when you contact Support with this bug, they refer to this issue!  "Try this, try that, maybe it works, oh, and we are doing our best". Meanwhile, its still on the long term list.  I suspect customers are being pushed towards Cloud (where everything is better and works 100% one must presume).

            Tip from Support: don't forget to Wacht the issue and click affected custormers.  That will definitely get this thing moving (NOT).

            Martin E added a comment - - edited and what happens when you contact Support with this bug, they refer to this issue!  "Try this, try that, maybe it works, oh, and we are doing our best" . Meanwhile, its still on the long term list.  I suspect customers are being pushed towards Cloud (where everything is better and works 100% one must presume). Tip from Support: don't forget to Wacht the issue and click affected custormers .  That will definitely get this thing moving (NOT).

            Morten Stensgaard added a comment -

            6 months have passed since I complained last and this bug have still not been resolved

            It is so easy to reproduce and quite easy to hit in the UI of Jira.

            Incredible that this is still on a "Long Term Backlog" - The regression bug was "introduced" in Jira 9.

            Not only is Datacenter products not getting any new valuable features to the end users(development have almost halted) - The product is actually getting worse/broken.

            Morten Stensgaard added a comment - 6 months have passed since I complained last and this bug have still not been resolved It is so easy to reproduce and quite easy to hit in the UI of Jira. Incredible that this is still on a "Long Term Backlog" - The regression bug was "introduced" in Jira 9. Not only is Datacenter products not getting any new valuable features to the end users(development have almost halted) - The product is actually getting worse/broken.

            Martin E added a comment -

            its still on the long term backlog! get you act into gear Atlassian and get this fixed a.s.a.p. please  

            Martin E added a comment - its still on the long term backlog! get you act into gear Atlassian and get this fixed a.s.a.p. please  

              ddudziak Stasiu
              458e633c07a6 Jose Antonio Uribe
              Affected customers:
              85 This affects my team
              Watchers:
              126 Start watching this issue

                Created:
                Updated:
                Resolved: