Incomplete Dependency on Backup Settings Configuration

[keyurk-emipro]

Preconditions (*)

1. Magento ver. 2.3.1

Steps to reproduce (*)

1. Go to Store > Configuration > System > Advanced > Backup Settings
2. Enable Backup => Yes
3. Enable Scheduled Backup => Yes
4. Enable Backup => No

Expected result (*)

1. All fields Must be Hidden on Enable Backup => No

Actual result (*)

1. Only Enable Scheduled Backup are dependable on Enable Backup Field.
2. And Other 4 fields depend on Enable Scheduled Backup.

[m2-assistant]

Hi @keyuremipro. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[m2-assistant]

Hi @AlexWorking. 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.

[magento-engcom-team]

✅ Confirmed by @AlexWorking
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99377 were created

Issue Available: @AlexWorking, 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 @keyuremipro. Thank you for your report.
The issue has been fixed in #22475 by @keyuremipro in 2.3-develop branch
Related commit(s):

• 60e862f64975378c8c2d269fdde1d97d6621275c

The fix will be available with the upcoming 2.3.2 release.

[magento-engcom-team]

Hi @keyuremipro. Thank you for your report.
The issue has been fixed in #22499 by @keyuremipro in 2.2-develop branch
Related commit(s):

• bd0613a10f5bdfc554361c39b7b43072f3395868

The fix will be available with the upcoming 2.2.9 release.