[Issue] Clarified Attribute Option already exists response #39943
Description
This issue is automatically created based on existing pull request: #39941: Clarified Attribute Option already exists response
Description (*)
Replaced the awkward phrase "Get new file name if the same is already exists" with a clearer and grammatically correct version: "Get a new file name if one already exists." This improves readability and user understanding.
Same for the attribute option response.
Manual testing scenarios (*)
- pushing an already existing attribute option to the attribute option api endpoint.
Questions or comments
First time PR to Magento. Please let me know if i need to do something else.
Contribution checklist (*)
- Pull request has a meaningful description of its purposeAll commits are accompanied by meaningful commit messagesAll new or changed code is covered with unit/integration tests (if applicable)README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an updateAll automated tests passed successfully (all builds are green)
Metadata
Metadata
Assignees
Labels
Use with concrete module component label E.g. "Component: Api" + "Catalog"Gate 3 Passed. Manual verification of the issue completed. Issue is confirmedMay be fixed according to the position in the backlog.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branch
Type
Projects
Milestone
Relationships
Participants
Activity
m2-assistant commentedon May 27, 2025
Hi @engcom-Bravo. 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: 👇
Area: XXXXXlabel to the ticket, indicating the functional areas it may be related to.2.4-developbranchDetails
- If the issue is reproducible on2.4-developbranch, please, add the labelReproduced 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!
Issue: Confirmedonce verification is complete.engcom-Bravo commentedon May 28, 2025
Hi @J0rdyV,
Thanks for your reporting and collaboration.
Could you please elaborate the steps to reproduce and if possible please provide us screenshots or screencast.
Thanks.
engcom-Bravo commentedon Jun 17, 2025
Hi @J0rdyV,
This issue is being closed since it has not been updated in a long time.Please feel free to reopen or raise a new ticket if the issue still exists.
Thanks.
engcom-Bravo commentedon Sep 5, 2025
Hi @J0rdyV,
We have tried to reproduce the issue in Latest 2.4-develop instance and we are able to reproduce the issue.Hence Confirming the issue.
Thanks.
github-jira-sync-bot commentedon Sep 5, 2025
✅ Jira issue https://jira.corp.adobe.com/browse/AC-15473 is successfully created for this GitHub issue.
m2-assistant commentedon Sep 5, 2025
✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.