Deleting a custom option affects / removes other custom options

[ProceduralUserName]

Preconditions and environment

Magento 2.4.7 p-3

Steps to reproduce

(Outcomes differ based on steps taken)

Setup:

• Create a new product
• Fill out required fields
• Scroll down to customizable options
• Create 4 custom fields: Field1, Dropdown1, Dropdown2, Radiobutton1.
• For each, fill in required fields with dummy data.
• For option type choose these, in order:
  - Field
  - Dropdown
  - Dropdown
  - Radiobuttons
• Make sure to add and populate Dropdown1, Dropdown2 and Radiobutton1's values fields.
• Save product
  Reproduce:
• Delete Field option
  OR
• Delete Dropdown1
  OR
• Delete Dropdown2

Expected result

Respective field is deleted and other fields remain the same as they were.

Actual result

If Field option was deleted:

• Field option is removed (Correct action)
• Dropdown1’s values are removed
• Dropdown1’s option type is reset to “--please select–” and cannot reselect Dropdown as an option type.
  If Dropdown1 was deleted:
• Field1 option type is reset to –”please select–” and cannot reselect Field as an option type.
• Dropdown1 is removed (Correct action)
• Dropdown2’s values are removed
• Radiobutton1’s values jump into Dropdown2’s values.
• Radiobutton1’s values are empty
  If Dropdown2 was deleted:
• Field1 option type is reset to –”please select–” and cannot reselect Field as an option type.
• Dropdown2 is removed (Correct action)
• Radiobutton1’s values are removed

Additional information

First post here, if there's any information I'm missing that I should add let me know.

Thanks.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ProceduralUserName. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[ProceduralUserName]

@magento I am working on this

[m2-assistant]

Hi @ProceduralUserName! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[ProceduralUserName]

@magento add to contributors team

[m2-assistant]

Hi @ProceduralUserName! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[ProceduralUserName]

@magento I am working on this

[ProceduralUserName]

@magento give me 2.4.7 instance

[m2-assistant]

Hi @engcom-Delta. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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.

[engcom-Delta]

Hi @ProceduralUserName ,

Thanks for your reporting and collaboration.
We have verified the issue in Latest 2.4 develop instance, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce
1 . Create a new product
2. Fill out required fields
3. Scroll down to customizable options
4. Create 4 custom fields: Field1, Dropdown1, Dropdown2, Radiobutton1.
5. For each, fill in required fields with dummy data.
6. For option type choose these, in order:

• Field
• Dropdown
• Dropdown
• Radiobuttons

7. Make sure to add and populate Dropdown1, Dropdown2 and Radiobutton1's values fields.
8. Save product
9. Remove field option, observe drop down option 1 is not deleted.
   
10. Now, Remove Drop down 1, Observe drop down 2 options and radio button is displaying as expected
    

Can you please re-verify and confirm if you are still facing the issue.
Thanks.