[Issue] set image rolls only if is_required is true

[in-session]

Preconditions and environment

Especially when managing many product images with different functions, it often happens that the wrong image roles are used when creating products. Here the field is_required should be used to control which roles are necessary by default. An image role does not mean that it has to be filled, as long as it is not an is_required.

Magento version 2.4.6-p5

Steps to reproduce

1. create a new product attributes media/images
2. then create a new article and upload the image

Expected result

all roles are assigned to the first picture

Actual result

only necessary roles should be assigned to the first image

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] 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”.

https://github.com/magento/magento2/assets/16542619/acfc304e-71f2-4351-a98f-7c54347f257a

Productt attribute media / image should be available is_required to automatically assign the image role when creating a product:

[m2-assistant[bot]]

Hi @in-session. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[in-session]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @in-session. Thank you for your request. I'm working on Magento instance for you.

[m2-assistant[bot]]

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: :point_down:

• [ ] 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

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

[magento-deployment-service[bot]]

Hi @in-session, here is your Magento Instance: https://d92b638996c3eec19ceb974d4b9b09d9.instances-prod.magento-community.engineering Admin access: https://d92b638996c3eec19ceb974d4b9b09d9.instances-prod.magento-community.engineering/admin_cf94 Login: 4fad2615 Password: ea9f59be9111

[engcom-Bravo]

Hi @in-session,

Thanks for your reporting and collaboration.

We have checked the issue in Latest 2.4-develop instance we are not able to see the Values Required option for the Media image attribute type.

As per the Magento dedocs https://docs.magento.com/user-guide/v2.3/stores/attributes-input-types.html when we create media image type attribute it becomes an additional image type, along with Base, Small, and Thumbnail.

Could you please let us know if we are missing anything.

Thanks.

[in-session]

@engcom-Bravo That's not quite what I mean, even if I can exclude it from the product gallery. Is the newly created role always automatically assigned to the first image:

Wrong:

So the field is_required yes/no should be used to determine whether the image role should be assigned automatically. Or a new field in which you can say which role should automatically be assigned to the first image.

Because all roles are always set to the first image, the images would be all over the place and that is not effective:

$product->getResource()->getAttribute('key_point_1')->getFrontend()->getValue($product);
$product->getResource()->getAttribute('key_point_2')->getFrontend()->getValue($product);
$product->getResource()->getAttribute('key_point_3')->getFrontend()->getValue($product);

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://d92b638996c3eec19ceb974d4b9b09d9.instances-prod.magento-community.engineering Admin access: https://d92b638996c3eec19ceb974d4b9b09d9.instances-prod.magento-community.engineering/admin_4b84 Login: 01c693e7 Password: bfbaf2b5bcf5

[in-session]

This only makes sense if they are necessary fields, an image role should be set by default when you assign it to the image role. https://docs.magento.com/user-guide/v2.3/catalog/product-image-upload.html#assign-roles

[engcom-Bravo]

Hi @in-session,

Thanks for your update.

For the Media image type attribute there will be no is_required field hence we are not able to set whether it is required or not As per the Magento devdocs when we create Media image type attribute it will be an additional image type and it is an expected behaviour.is_required field is required for image attribute.

Hence to proceed further we are marking this as a feature request.

Thanks.