Magento CE 2.2.2 - Set Product as New From (Invalid input datetime format) Locale AU

[gilbertsohal]

Preconditions

1. Magento CE 2.2.2
2. PHP version: 7.0
3. Locale AU

Steps to reproduce

Set Locale AU

1. Stores > Configuration >General > General > Locale Options
   Set Default Country to Australia and Locale to AU
   Step 1 Screenshot
   https://prnt.sc/ggek4e

2. Admin > Account Settings > My Account > Account Information
   Set Interface Locale to English Australia
   Step 2 Screenshot
   https://prnt.sc/ggelkj

3. Stores > Configuration >Catalog > Catalog >Date & Time Custom Options
   Use JavaScript Calendar to Yes and Date Fields Order to dd/mm/yyyy
   Step 3 Screenshot
   https://prnt.sc/hyqrpk

4. Date format working fine on frontend (dd/mm/yyyy)
   Step 4 Screenshot
   https://prnt.sc/hyqs9a

4. Configurable Product Set Product as New From
   Set Product as New From as dd/mm/yyyy format
   Step 5 Screenshot
   https://prnt.sc/hyqu91

Expected result

1. Configurable Product Set Product as New From Save without error with dd/mm/yyyy format

Screenshot 1
https://prnt.sc/hyqv39

Actual result

1. Configurable Product Set Product as New From throw error with dd/mm/yyyy format
   Screenshot 1
   https://prnt.sc/hyquvj

[gilbertsohal]

@magento-engcom-team

Could you please guide me what to do?

[magento-engcom-team]

@gilbertsohal, thank you for your report.
We've acknowledged the issue and added to our backlog.

[gilbertsohal]

@magento-engcom-team

Have you solved this issue in 2.2.3?

[ioweb-gr]

@gilbertsohal I'm on a 2.2.3 installation and it's still occurring for me.

[ioweb-gr]

Any news on this one?

[orlangur]

Such issue definitely shouldn't require more than a year to be fixed. Triggering re-check.

[m2-assistant]

Hi @VasylShvorak. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[VasylShvorak]

Issue isn't reproduced by described steps on clean 2.3-develop