Report Value doesn't matching - "Year-To-Date Starts"

[vishvesshah]

Report Value doesn't matching - "Year-To-Date Starts".

Preconditions (*)

1. Magento 2.3.4,2.3.3

Steps to reproduce (*)

1. Login to Adminpanel.
2. Go to Stores >> Configuration >> General >> Reports
3. From Dashboard tab >> Select "Year-To-Date Starts".

Expected result (*)

1. It should select the correct value, if I have selected month 12 then it should select 12 only.

Actual result (*)

1. If you have selected 12 then it will take the month "1", if 11 then it will select month 12

Please see the screenshot below. You will be able to see the issue with enabling the developer toolbar from browser only.

[m2-assistant]

Hi @vishvesshah. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@vishvesshah do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @Priya-V-Panchal. 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.4-develop branch

  Details

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

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @krishprakash. 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.

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

[Priya-V-Panchal]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @Priya-V-Panchal. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @Priya-V-Panchal, here is your Magento instance.
Admin access: https://i-27086-2-4-develop.instances.magento-community.engineering/admin_2358
Login: 782f09ab Password: b5909a680f3f
Instance will be terminated in up to 3 hours.

[samikshakrish]

@magento give me 2.4-develop instance - upcoming 2.4.x release

[magento-engcom-team]

Hi @samikshakrish. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @samikshakrish, here is your Magento instance.
Admin access: https://i-27086-2-4-develop.instances.magento-community.engineering/admin_86fe
Login: d073e204 Password: cdb56e4d4d4c
Instance will be terminated in up to 3 hours.

[samikshakrish]

@magento give me 2.4-develop instance - upcoming 2.4.x release

[magento-engcom-team]

Hi @samikshakrish. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @samikshakrish, here is your Magento instance.
Admin access: https://i-27086-2-4-develop.instances.magento-community.engineering/admin_13cd
Login: 62e1d8fe Password: bb111f3785d3
Instance will be terminated in up to 3 hours.

[samikshakrish]

Verified the issue on latest instance .

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-32028 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @vishvesshah. Thank you for your report.
The issue has been fixed in #27088 by @Priya-V-Panchal in 2.4-develop branch
Related commit(s):

• d03d8e1e2a705e8677e680f01f0e04e899daa305
• 2ec8bf5d59cc858979e83d3786b7cb7ee563ad1b
• 2410cbb760e1e88fa5c0681fa35baaf3686dd64a
• a2a865c499ba8eed3c2ea24975d3c8f4a037d475

The fix will be available with the upcoming 2.4.0 release.