Admin config section not expanded when fields are required.

[qsolutions-pl]

Preconditions (*)

1. Magento 2.3.3 / 2.3.2 Open Source

Steps to reproduce (*)

1. Create a new module that adds new system configuration
2. In this system configuration add 2 group of fields
3. For first group make all fields not required
4. For second group make at least 1 field required
5. Go to that section in admin panel
6. Make sure both sections are not expanded (by default they should not be)
7. Try to save system config

Expected result (*)

1. System should expand tab with required fields and scrolls to it / them

Actual result (*)

1. Nothing happens, from customer / UX point of view system hangs and there is no error message

[m2-assistant]

Hi @qsolutions-pl. 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.

@qsolutions-pl 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 @shikhamis11. 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.

[m2-assistant]

Hi @shikhamis11. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

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

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

[m2-assistant]

Hi @vikalps4. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[qsolutions-pl]

@sdzhepa this is in progress for 28 days, any update?

[qsolutions-pl]

@sdzhepa another 14 days have passed, how is progress on this task? @magento-engcom-team can I have any update on this?

[sdzhepa]

Hello @qsolutions-pl

I just set label Dev In Progress because

vikalps4 self-assigned this on Jan 27

But seems @vikalps4 is not working on it and I can unassign him
So, this issue is ready for development - feel free to propose PR with fix

[Bartlomiejsz]

@magento I am working on this

[magento-engcom-team]

Hi @qsolutions-pl. Thank you for your report.
The issue has been fixed in #28285 by @Bartlomiejsz in 2.4-develop branch
Related commit(s):

• a7fa47b4a30dbb86c90d615474e566c5535c800d
• c842d73772943284f4633c3c14db1eade1b8c928
• 9d70a32057c91f89d994c24b8de83e44972c18b5
• ac5ce560880c0ea1963a2a99294fab60317d5c65

The fix will be available with the upcoming 2.4.1 release.