Unable to sort catalog by Custom Attribute of type Dropdown

[gwharton]

Preconditions and environment

• 2.4.5
• Sample data

Steps to reproduce

To test this, we will create a test attribute and assign values to the products in the sample data category "Bag", and then attempt to sort by the test attribute.

- Stores -> Attributes -> Product
 - Add New Attribute
  - Properties Tab
   - Default Label = test
   - Catalog Input Type for Store Owner = Dropdown
   - Add Option "first"
   - Add Option "second"
   - Add Option "third"
   - Add Option "fouth"

  - Storefront Properties Tab
   - Used for sorting in product listing = Yes
  - Leave all other options as default
 - Save Attribute

- Stores >Attributes -> Attribute Set
 - Select Bag
 - Drag test attribute into Product Details group
- Save

- Catalog -> Products -> Add filter to only show products in Attribute Set "Bag"
- Configure the following products to have test attribute values

• Joust 24-MB01 - fourth
• Fusion 24-MB02 - third
• Crown Summit 24-MB03 - second
• Strive 24-MB04 - first
• Wayfarer 24-MB05 - fourth
• Rival Field 24-MB06 - third

To make testing easier, remove all other products that have attribute set of "Bag" to leave only the above 6 items in the filtered view.

- Clear cache
- Go to frontend and browse to the Bag category.
- Sort by test

Expected result

The products should be ordered by test attribute. (Attribute value in brackets)

1. Strive (first)
2. Crown Summit (second)
3. Fusion (third)
4. Rival Field (third)
5. Joust (fourth)
6. Wayfarer (fourth)

Actual result

Additional information

No response

Release note

Products can now be sorted on the Product Listing pages by custom attribute of Dropdown type.

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 @gwharton. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

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

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

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

  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.

[engcom-Delta]

Hi @gwharton ,
Thank you for raising an issue , We tried to reproduce the issue on Magento 2.4.5 instance , we could not find out manage options at Stores-->Attributes-->Product. Please review the steps provided.

[gwharton]

I have updated the steps to reproduce with more detailed layout of required steps to reproduce.

[gwharton]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @gwharton. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @gwharton, here is your Magento Instance: https://89ee2a9d58500ec83f044e4cd4637101.instances.magento-community.engineering
Admin access: https://89ee2a9d58500ec83f044e4cd4637101.instances.magento-community.engineering/admin_5b54
Login: 45427b0a
Password: 601251524e7e

[gwharton]

Confirmed on 2.4-develop instance.

[engcom-Delta]

Hi @gwharton ,

Thank you for providing inputs and we tried to reproduce the issue on Magento 2.4 develop , issue is reproducible.
Actually products are getting sorted by its position instead of custom sort option.

Hence , issue has been confirmed.

Please find below screenshots for reference.

on backend setup:

On frontend