Magento DevBlog

Welcome to the February Edition of Our Community-Led Prioritization Process Update!

February brings new opportunities, ongoing collaborations, and exciting updates from our community-led initiatives. Your engagement continues to be the driving force behind our collective success, and we truly appreciate your contributions.

Stay tuned for the latest developments, key achievements, and upcoming ways to get involved in shaping our shared priorities. Let’s make this another impactful month together!

I’m excited to announce that the following “community_picked” functionalities and fixes made it to our code base this month. 

Magento 2 Repo –

• Product layout based on attribute_set
• Correct spelling of variables for customer address
• fix joinprocessor behavior with consecutive calls
• Fix to save middle name in the quote for guest
• Fix bad phpdoc \Magento\Sales\Model\Order\Email\Container\Template::$id property
• Dont throw console error for customer data if the request is cancelled or blocked by browser.
• GraphQL: add category_url_path to ProductAttributeFilterInput
• Fixed issue Add to Wishlist with product custom option file upload not working Magento 2.4.6
• GraphQl Product visibility for search results
• Do not load Shipment and Creditmemos collections on Order model
• Update js.js DOM text reinterpreted as HTML
• Removed unused Type configuration
• add isMultipleFiles property to image form element template
• Feature/php8.1 constructor property promotion wee graph ql

Hall of Fame

Huge shoutout to our rockstar contributors whose PRs made it into the codebase this month. Thank you again for sharing your time and knowledge with the community. Let’s give them a virtual round of applause!

Based on the votes from the community, Following PRs made it to the community dashboard for processing this month.

Magento2 Repo –

Page Builder Repo –

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far for Magento2 repo and Page Builder repo.    

Magento2 Repo –

Page Builder Repo –

Please check the real time status and progress of these community picked PRs (based on your votes) on the community dashboards -  magento2 and page builder

If you missed our earlier updates on community prioritization process, please visit the  DevBlog.   

How to participate in the process:  

• You can vote on your favourite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link to the repositories -  https://github.com/magento/magento2/pulls , https://github.com/magento/magento2-page-builder/pulls . Here is a step-by-step guide to help you upvote a pull request, which you can refer next time to upvote the PR
  https://community.magento.com/t5/Magento-DevBlog/Guide-for-PR-Upvote/ba-p/563570

• Communications for voting window is posted on slack. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard to work on, with a purple label - “Project:Community Picked". 

• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  

We value your feedback! The Community-Led Prioritization Process is your opportunity to shape the future of Magento Open Source and Adobe Commerce. Share your thoughts on the process, suggest improvements, and let us know which contributions matter most to you. Your input will guide the development of our platform and ensure it reflects the needs of our community. Don’t miss your chance—complete the feedback form by February 28th. Together, we can make a difference!

👉 Complete the Feedback Form Here  

We deeply appreciate the ongoing enthusiasm and support from each of you. Thank you for being an integral part of our journey and for your dedication to making the Magento Open Source community truly exceptional.

Welcome to the January Edition of Our Community-Led Prioritization Process Update!

Happy New Year! As we step into 2025, we hope this year brings you joy, success, and new opportunities. January marks the beginning of another exciting chapter, and we're thrilled to share updates on our community-led initiatives. As we progress through another eventful month, your continued engagement remains the cornerstone of our collective success.

Stay tuned for the latest developments, achievements, and upcoming opportunities to contribute to shaping our shared priorities. I’m excited to announce that the following “community_picked” functionalities and fixes made it to our code base this month. 

Magento 2 Repo -

• Make ImageMagick Adapter compatible with php8 (Implicit conversion from float to int)
• Remove all marketing get parameters to minimize the cache using built-in FPC
• Improve cron error logging
• No update must be a boolean, int given for bin/magent sampledata:deploy|remove
• avoid a misconfiguration infinite loop
• Login as customer opt-in checkbox not translatable
• PHPDoc correction spelling
• Use Object Manager for ModeConfigured
• Fix typo in PHPDoc block
• add sourceMap generation for less files in developer mode
• Task/38939 docblock change
• Fix bad phpdoc Magento\Framework\App\Config\ScopeConfigInterface
• Fixed timezone of order_date field returned from graphql customerOrders query
• Input type file required field validation bug fix
• Restores backwards compatibility with TinyMCE plugins again (after it broke with introduction with T...

Hall of Fame

Huge shoutout to our rockstar contributors whose PRs made it into the codebase this month. Thank you again for sharing your time and knowledge with the community. Let’s give them a virtual round of applause!

Based on the votes from the community, following PRs made it to the community dashboard for processing this month.

Magento2 Repo -

Page Builder Repo -

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far for Magento2 repo and Page Builder repo.  

Magento 2 Repo - 

Page Builder Repo - 

Please Note: We have removed PR #39469 from community picked dashboard, as it has now been targeted to 2.5 release line. We are currently processing PRs intended for the 2.4 branch only.

Please check the real time status and progress of these community picked PRs (based on your votes) on the community dashboards -  magento2 and page builder

If you missed our earlier updates on community prioritization process, please visit the  DevBlog.   

How to participate in the process:  

• You can vote on your favourite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link to the repositories -  https://github.com/magento/magento2/pulls , https://github.com/magento/magento2-page-builder/pulls . Here is a step-by-step guide to help you upvote a pull request, which you can refer next time to upvote the PR
  https://community.magento.com/t5/Magento-DevBlog/Guide-for-PR-Upvote/ba-p/563570

• Communications for voting window is posted on slack. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard to work on, with a purple label - “Project:Community Picked". 

• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  

We value your feedback! The Community-Led Prioritization Process is your opportunity to shape the future of Magento Open Source and Adobe Commerce. Share your thoughts on the process, suggest improvements, and let us know which contributions matter most to you. Your input will guide the development of our platform and ensure it reflects the needs of our community. Don’t miss your chance—complete the feedback form by February 28th. Together, we can make a difference!

👉 Complete the Feedback Form Here

We deeply appreciate the ongoing enthusiasm and support from each of you. Thank you for being an integral part of our journey and for your dedication to making the Magento Open Source community truly exceptional.

Welcome to the December edition of our Community Led Prioritization Process Update. As we progress through another eventful month, I’m excited to announce that the following “community_picked” functionalities and fixes made it to our code base this month.

Magento 2 Repo -  

• Implement command loader to reduce initialization time of Magento CLI 

• Fix usage of EAV cache type 

• Improved error message when requirejs fails to load a component. 

• Improved date format in js console: switch from 12 hour to 24 hour format and adding timezone at the... 

• Using virtual type to configure plugin, interceptor method cannot be generated correctly in setup:di... 

• Performance optimisation large shopping carts by preventing call duplicate getActions 

• Fixed mobile version of checkout progress bar

Page Builder Repo -  

• Template Preview Images Incorrectly Saved to Media Directory

Hall of Fame

Huge shoutout to our rockstar contributors whose PRs made it into the codebase this month. Thank you again for sharing your time and knowledge with the community. Let’s give them a virtual round of applause! 

Based on the votes from the community, following PRs made it to the community dashboard for processing this month.

Magento2 Repo –

Page Builder Repo –

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far for Magento2 repo and Page Builder repo.  

Magento 2 Repo -

Page Builder Repo -

Please check the real time status and progress of these community picked PRs (based on your votes) on the community dashboards -  magento2 and page builder

If you missed our earlier updates on community prioritization process, please visit the  DevBlog.   

How to participate in the process:  

• You can vote on your favourite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link to the repositories -  https://github.com/magento/magento2/pulls , https://github.com/magento/magento2-page-builder/pulls . Here is a step-by-step guide to help you upvote a pull request, which you can refer next time to upvote the PR
  https://community.magento.com/t5/Magento-DevBlog/Guide-for-PR-Upvote/ba-p/563570

• Communications for voting window is posted on slack. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard to work on, with a purple label - “Project:Community Picked". 

• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  

We are grateful for the ongoing enthusiasm and support from each of you, Thank you for being an integral part of our journey and for your dedication in making Magento Open Source community truly exceptional.

Community Led Prioritization Process Update – November 2024

The Magento Open Source Community assists in prioritizing pull requests developed by Adobe or community contributors. Community members can vote for their favourite pull requests in the repositories by adding a 👍 reaction. Here’s a step-by-step guide to help you upvote a pull request.

Step 1: Log in to Github and access the magento2 and pagebuilder repositories.

Magento2 repository - https://github.com/magento/magento2/pulls

Pagebuilder repository - https://github.com/magento/magento2-page-builder/pulls

Step 2: Scroll through the list of open pull requests.

Step 3: Click on the pull request you wish to endorse.

Step 4: Scroll through the pull request description

Step 5: Click on the emoji icon of the description and select the upvote 👍 reaction

Step 6: You can view the upvote 👍 reaction in the description

Now you know how to upvote a pull request! Engaging with pull requests through upvote reaction can help us pick the most voted pull request under community prioritization framework. You can sort the list of PRs by the number of 👍 reactions. To do this, either manually sort the list or enter the following query in the search bar: “sort:reactions-+1-desc”.

Welcome to the October edition of our Community Led Prioritization Process Update. As we progress through another eventful month, I’m excited to announce that the following “community_picked” functionalities and fixes made it to our code base this month. 

Magento 2 Repo :

• Remove unnecessary scripts review summary
• Add permission check for "reload data" data button
• Pass custom attributes to current link via XML
• Ability to define Area for dev:di:info CLI command
• Rendering the critical css inline event via csp

Page Builder Repo :

• Fix finding child content-type elements in stage-builder
• Bug fixed when using the decimal number in slidesToShow.

Based on the votes from the community, Following PRs made it to the community dashboard for processing.

Magento2 Repo :

Page Builder Repo :

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far for Magento2 repo and Page Builder repo.  

Magento 2 Repo :

Page Builder Repo :

Please note: We have removed PR #38920 from community picked dashboard  , as it has now been targeted to 2.5 release line. We are currently processing PRs intended for the 2.4 branch only.

Please check the real time status and progress of these community picked PRs (based on your votes) on the community dashboards -  magento2 and page builder

If you missed our earlier updates on community prioritization process, please visit the  DevBlog.   

How to participate in the process:  

• You can vote on your favourite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link to the repositories -  https://github.com/magento/magento2/pulls , https://github.com/magento/magento2-page-builder/pulls  

• Communications for voting window is posted on slack. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard to work on, with a purple label - “Project:Community Picked". 

• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  

We are grateful for the ongoing enthusiasm and support from each of you, Thank you for being an integral part of our journey and for your dedication in making Magento Open Source community truly exceptional.

Welcome to the September edition of our Community Prioritization Process Update. As we move through another eventful month, I’m excited to announce that the following “community_picked” functionalities and fixes made it to our code base this month. 

Magento 2 Repo : 

• Area code not set" after update to 2.4.5-p8
• Issue at product import when provided with custom options-type
• Use compiled config for generated data instead of general config
• Remove references to files from extjs which got removed
• Remove 'pub/' directory from paths in css source maps when compiling using grunt
• Minor cleanup: fixed wrong usage of sprintf
• Date and Time Format for Custom Option Not Working
• Fix issue when compiling statics with multiple jobs
• GraphQL type error fix
• Fixes incorrect classes being referenced in Magento modules.

Based on the votes from the community, Following PRs made it to the community dashboard for processing.

Magento2 Repo :

Page Builder Repo :

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far for Magento2 repo and Page Builder repo.  

Magento 2 Repo :

Page Builder Repo :

Please check the real time status and progress of these community picked PRs (based on your votes) on the community dashboards -  magento2 and page builder

If you missed our earlier updates on community prioritization process, please visit the  DevBlog.   

How to participate in the process:  

• You can vote on your favourite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link to the repositories -  https://github.com/magento/magento2/pulls , https://github.com/magento/magento2-page-builder/pulls  

• Communications for voting window is posted on slack. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard to work on, with a purple label - “Project:Community Picked". 

• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  

We are grateful for the ongoing enthusiasm and support from each of you, Thank you for being an integral part of our journey and for your dedication in making Magento Open Source community truly exceptional.

Welcome to the latest edition of our Community Prioritization Process Update. As we move through another dynamic month, I am very pleased to share that based on the votes from the community, Following PRs made it to the community dashboard for processing.

Magento2 Repo-

Page Builder Repo- No PR was picked as no upvotes were marked.

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far for Magento2 repo and Page Builder repo.  

Magento 2 Repo-

Page Builder Repo-

Please check the real-time status and progress of these community picked PRs (based on your votes) on the community dashboards -  magento2 and page builder

We have 2 open Mainline Pull Requests that we expect to get merged soon into the code base - https://github.com/magento-commerce/magento2ce/pull/9174 and https://github.com/magento-commerce/magento2ce/pull/9186

If you missed our earlier updates on community prioritization process, please visit the  DevBlog.   

How to participate in the process: 

• You can vote on your favorite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link to the repositories -  https://github.com/magento/magento2/pulls , https://github.com/magento/magento2-page-builder/pulls  

• Communications for voting window is posted on slack. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard to work on, with a purple label - “Project:Community Picked". 

• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review. 

We are grateful for the ongoing enthusiasm and support from each of you, Thank you for being an integral part of our journey and for your dedication in making Magento Open Source community truly exceptional.

Welcome to the latest edition of our Community Prioritization Process Update. As we move through another dynamic month, I am very pleased to share that the following functionalities and fixes made it to our code base this month. 

Magento 2 Repo-

• Add logic check only import css from enabled modules
• Google GTag add ecommerce data fix.
• Fix wording of filter item on layered navigation
• Display backordered quantity if the order item has them
• Depend directives updated in failed payment email template
• Remove jobs no longer referenced in the codebase
• Code cleanup and add new critical head block and move critical css before assets

Mainline Pull Requests - https://github.com/magento-commerce/magento2ce/pull/8954 and https://github.com/magento-commerce/magento2ce/pull/9065

Page Builder Repo-

The pull requests merged so far are-

• Tailwindui css layout support - colon is not accepted by the pattern
• Removes less code that uses frontend definitions in an admin html file
• Community - Width & Height attribute - Pagebuilder image
• Add YouTube NoCookie Support

Mainline Pull Requests - https://github.com/magento-commerce/magento2-page-builder/pull/299 and https://github.com/magento-commerce/magento2-page-builder/pull/330

Based on the votes from the community, following PRs made it to the community dashboard for processing.

July Batch :

Magento2 Repo-

Page Builder Repo-

• Ignore styles which no longer apply.
• Ensure children do not become orphans

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far for Magento2 repo and Page Builder repo.  

Magento 2 Repo :

Page Builder Repo-

Please check the real time status and progress of these community picked PRs (based on your votes) on the community dashboards -  magento2 and page builder

If you missed our earlier updates on community prioritization process, please visit the DevBlog.   

How to participate in the process:  

• You can vote on your favourite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link to the repositories -  https://github.com/magento/magento2/pulls , https://github.com/magento/magento2-page-builder/pulls  

• Communications for voting window is posted on slack. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard to work on, with a purple label - “Project:Community Picked". 

• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  

We are grateful for the ongoing enthusiasm and support from each of you, Thank you for being an integral part of our journey and for your dedication in making Magento Open Source community truly exceptional.

I am very pleased to share that the following functionalities and fixes made it to our code base this month. 

Mainline Pull Requests -  https://github.com/magento-commerce/magento2ce/pull/8892 and https://github.com/magento-commerce/magento2ce/pull/8850.  

Based on the votes from the community, following PRs made it to the community dashboard for processing.

April Batch: 

Magento2 repo 

Page Builder Repo - 

• Width & Height attribute - Pagebuilder image 

May Batch: 

Magento2 repo 

Page Builder Repo - 

• PageSpeed Insights - Ensure text remains visible during webfont load 

• Removes less code that uses frontend definitions in an adminhtml file 

• Fixes: Bundle product with only one product in required bundle option not being added to cart with b... 

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far for magento2 repo.  

 Please check the real time status and progress of these community picked PRs (based on your votes) on the community dashboards -  magento2 and page builder  

If you missed our earlier updates on community prioritization process, please visit the  DevBlog.   

How to participate in the process:  

• You can vote on your favorite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link to the repositories -  https://github.com/magento/magento2/pulls , https://github.com/magento/magento2-page-builder/pulls  

• Communications for voting window is posted on slack. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard to work on, with a purple label - “Project:Community Picked". 

• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  

Thank you for your engagement and contribution to the Magento Open Source community! 

Community Prioritization Process Update – Feb & March 2024 

We picked a new batch of pull requests today under the community prioritization process. These are the ones that made it to the community dashboard. 

P.S - We are currently picking and processing PRs intended for 2.4 branch only. We will be happy to pull the ones that are not picked for processing despite high votes, if their target branch is updated and the PR is made ready to be reviewed. 

Here is the combined status of the pull requests worked on so far.  

Total - 166 

For real time status, please visit the community dashboard.    

If you missed our earlier updates on community prioritization process, please visit the  DevBlog. Follow  #commercecommunitymonthly  to view the monthly community newsletter that has a permanent section to share update on this process.  

How to participate in the process:  

• You can vote on your favorite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link for the repository -  https://github.com/magento/magento2/pulls   
• Communcations for voting window is posted on slack, LinkedIn, and X. When the voting window ends, we pick a batch of most up voted pull requests and add  them to the community dashboard to work on, with a purple label - “Project:Community Picked". 
• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  
• Feel free to reach out to me if you are interested in becoming a contributor or a maintainer for Magento Open Source. I will be happy to point you to the right resources.  

Thank you for your engagement and contribution to the Magento Open Source community!  

Happy 1st anniversary! 

This month marks the one-year anniversary for the Community Prioritization Process. We started this endeavor last year with 10 pull requests, and as of today, 146 pull requests have been included in this initiative. 

A huge shout out to everyone who contributed throughout the year to voting, reviewing, testing, and merging of all these code contributions. 

The following 10 pull requests were added to the community dashboard this month for processing, based on the votes from the community.  

P.S - If you are wondering about the first PR in the list not being included in the batch, here is why - we are currently processing PRs intended for 2.4 branch only. We will be happy to pull it on the community dashboard for processing if the target branch is updated and the PR is ready to be reviewed. 

Here is the combined status of the pull requests worked on so far.  

Total - 146 

For real time status, please visit the community dashboard.    

If you missed our earlier updates on community prioritization process, please visit the  DevBlog. You could also follow #commercecommunitymonthly  to view the monthly community newsletter that has a permanent section to share update on this process.  

How to get involved in the process:  

• You can vote on your favorite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link for the repository -  https://github.com/magento/magento2/pulls   
• Communications about voting window is posted on slack, LinkedIn, and X. When the voting window ends, we pick a batch of most up voted pull requests and add them to the community dashboard for processing, with a purple label - “Project:Community Picked". 
• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  
• Feel free to reach out to me if you are interested in becoming a contributor or a maintainer for Magento Open Source. I will be happy to point you to the right resources.  

Thank you for your engagement and contributions to the Magento Open Source community!  

We added these 15 pull requests to the community dashboard this month, based on your votes.  

Thank you to all the community members who voted! 

Community Prioritization Process is an initiative to empower the community to influence the Magento Open Source roadmap and codebase by upvoting the pull requests that brings most value to them. Adobe then picks the most up voted Pull Requests and adds them to the community dashboard to work on, with a purple label - “Project:Community Picked".  

Here is the combined status of the pull requests worked on so far.  

Total - 136 

Functionalities that made into the code base this month: 

• Improve product page loading speed 
• Replace JSON serializer with JSON Hex Tag (User module) 
• Admin Users unable to change front-end Logo in Design Config when in Single Store Mode 
• Add Cart Rule product subselect total incl. tax option 
• Improve cls pdp screen 
• Meta title issue on product page for Page title suffix 
• Missing field from configurable-products/sku/children Rest Endpoint 
• Fix file upload styles duplication in luma theme 
• Changes of GR(Greece) PostCode Pattern 
• Removed unused class from ProductRepository 

For real time status, please visit the community dashboard.    

Thank you to everyone who contributed to voting, coding, reviewing, testing, and merging of these enhancements and improvements.  

If you missed our earlier updates on community prioritization process, please visit the  DevBlog. You could also follow #commercecommunitymonthly  to view the monthly community newsletter that has a permanent section to share update on this process.  

How to get involved in the process:  

• You can vote on your favorite pull requests in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link for the repository -  https://github.com/magento/magento2/pulls   
• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  
• Feel free to reach out to me if you are interested in becoming a contributor or a maintainer for Magento Open Source. I will be happy to point you to the right resources.  

Thank you for your engagement and contribution to the Magento Open Source community! 

As usual, New York was an inviting venue for this annual Meet Magento event.  Meet Magento New York was the first Magento community event that I’ve attended, and just like before, this year’s event didn’t disappoint.  With multiple tracks of speakers from the community, and visitors from over 20 countries across the globe, this was a great opportunity to learn and share.

I am happy to share that the following functionalities, picked under the community prioritization process , based on the votes from the community, made it to the code base in September. These  will be available in 2.4.7-beta2 release: 

• Fixed issue Billing & Shipping address the same checkbox is empty 
• magento/magento2#37028: [Sales] Missing relation data when reorder 
• Added: SKU with configurable, group, bundle product Title 
• Fixed: Incorrect discount amount for whole cart 
• Log Aggregation fix on Checkout failure (group by reason, not Quote ID) 
• Import/Export - Fix 'entity values are mixed' exception when no valid data 
• Fixed: $row() undefined issue while inline edit after delete item from database 
• Fix for issue 27474-Feedback regarding invoice email being sent  
• Avoid divide-by-zero fatal error 
• Replaced CREATE TEMPORARY TABLE ... LIKEwith different approach 
• Update Ga.php to fix no revenue data in GA4 
• Show customer_grid indexer as green when realtime 
• Fixed duplicated ids to index by mview changelog 
• Removed unused plugin on protected method 
• feat: more informative error message on xml validation errors 
• [PHPMD] Add phpmd rule with ignoring of unused required parameters in the plugins 

• Add aspect ratio for catalog images and remove unnecessary script 
• Improve performance of DataObject magic calls and addData() 

Community Prioritization Process is an initiative to empower the community to influence the Magento Open Source roadmap and codebase by upvoting the pull requests that brings most value to them. Adobe then picks the most up voted Pull Requests and adds them to the community dashboard to work on, with a purple label - “Project:Community Picked". The voting window is open. We will pick the next batch on Oct 9, 2023. 

The following set was picked this month, to work on. Thank you to all those who participated in the process by voting on the PRs.  

Here is the combined status of the PRs (Pull requests) worked on so far. For real time status, please visit the community dashboard.  

Total – 121 

Thank you to everyone who contributed to voting, coding, reviewing, testing, and merging of these enhancements and improvements.  

If you missed our earlier updates on community prioritization process, please visit the  DevBlog. You could also follow #commercecommunitymonthly on LinkedIn to view the monthly community newsletter that has a dedicated section to share updates on this process.  

How to get involved in the process:  

• You can vote on your favorite PRs in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link for the repository - https://github.com/magento/magento2/pulls   
• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review.  
• Feel free to reach out to me if you are interested in becoming a contributor or a maintainer for Magento Open Source. I will be happy to point you to the right resources.  

Thank you for your engagement and contribution to the Magento Open Source community!  

We picked the following 15 pull requests in August under the community prioritization process  based on the votes from the community. Thank you to all the community members who voted! 

Community Prioritization Process is an initiative to empower the community to influence the Magento Open Source roadmap and codebase by upvoting the pull requests that brings most value to them. Adobe then picks the most up voted Pull Requests and adds them to the community dashboard to work on, with a purple label - “Project:Community Picked". We open the voting window every month, sometimes twice a month.  

Here is the combined status of the PRs (Pull requests) worked on so far. For real time status, please visit the community dashboard.  

Total - 106 

Thank you to everyone who contributed to voting, coding, reviewing, testing, and merging of these enhancements and improvements. 

We share a monthly update on the progress of PRs picked under this process. If you missed our earlier updates, please visit the  DevBlog. You could also follow #commercecommunitymonthly on LinkedIn to view the monthly community newsletter that has a dedicated section to share updates on this process. 

How to get involved in the process: 

• You can vote anytime on your favorite PRs in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link for the repository - https://github.com/magento/magento2/pulls  
• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review. 

• Feel free to reach out to me if you are interested in becoming a contributor or a maintainer for Magento Open Source. I will be happy to point you to the right resources. 

Thank you for your engagement and contribution to the Magento Open Source community! 

Magento Open Source 2.4.7-beta 1 was released last month (June) that included 25 community voted PRs picked under the Community Prioritization Process. Community Prioritization Process is an initiative to empower the community to influence the Magento Open Source roadmap and codebase by upvoting the pull requests that brings most value to them. Adobe then picks the most up voted Pull Requests and adds them to the community dashboard to work on, with a purple label - “Project:Community Picked". We open up the voting window every month and sometimes twice a month.  

Following functionalities made it to the code base month: 

1.  Fixed excel writer produces invalid files for numbers preceded by spaces 
2. Fixed issue Add to Wishlist with product custom option file upload not working 
3. Undefined index in TierPriceValidator.php 
4.  Remote storage issue 
5. GraphQl Product visibility for search results 

and these 9 are currently waiting for their turn in the merge queue: 

Here is the combined status of the PRs worked on so far. For real time status, please visit the community dashboard.  

Total - 91 

We picked the following 10 pull requests this month based on the votes from the community. Thank you to all the community members who voted! 

Thank you to everyone who contributed to voting, coding, reviewing, testing, and merging of these enhancements and improvements. 

If you missed our earlier updates on community prioritization process, please visit the  DevBlog. You could also follow #commercecommunitymonthly on LinkedIn to view the monthly community newsletter that has a dedicated section to share update on this process. 

How to get involved in the process: 

• You can vote on your favorite PRs in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link for the repository -  https://github.com/magento/magento2/pulls  
• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review. 
• Feel free to reach out to me if you are interested in becoming a contributor or a maintainer for Magento Open Source. I will be happy to point you to the right resources. 

Thank you for your engagement and contribution to the Magento Open Source community!  

Community Prioritization Process Update – June 2023 

This month we released Adobe Commerce and Magento Open Source 2.4.7-beta1 that includes over 150 quality fixes and enhancements along with 2.4.6-p1, 2.4.5-p3, 2.4.4-p4, and patches for extended support clients. 

The Magento Open Source 2.4.7-beta 1 release included 25 community voted PRs picked under the Community Prioritization Process. 

Community Prioritization Process is an initiative to empower the community to influence the Magento Open Source roadmap and codebase by upvoting the pull requests that brings most value to them. Adobe then picks the most up voted Pull Requests and adds them to the community dashboard to work on, with a purple label - “Project:Community Picked". We open up the voting window every month and sometimes twice a month.  

We picked 20 pull requests this month based on the votes from the community. Thank you to all the community members who voted! 

June 9th batch  

June 29th batch 

Here is the combined status of the pull requests worked on so far.  

Total: 81 

For real time status, please visit the community dashboard.   

Thank you to everyone who contributed to voting, coding, reviewing, testing, and merging of these enhancements and improvements. 

If you missed our earlier updates on community prioritization process, please visit the  DevBlog. You could also follow #commercecommunitymonthly on LinkedIn to view the monthly community newsletter that has a permanent section to share update on this process. 

How to get involved in the process: 

• You can vote on your favorite PRs in the repository by adding 👍reaction. Make sure you are logged in to your GitHub account. Link for the repository -  https://github.com/magento/magento2/pulls  
• If you are a codebase maintainer, please check the community dashboard for PRs that are available for review. 
• Feel free to reach out to me if you are interested in becoming a contributor or a maintainer for Magento Open Source. I will be happy to point you to the right resources. 

Thank you for your engagement and contribution to the Magento Open Source community! 

I’m thrilled to announce the latest release for the Magento Open Source community.  What a way to kick off summer! Today, Adobe released the Magento Open Source 2.4.7-beta 1 patch.  This is a huge step as it materializes the hard work and dedication from the community around the Community Prioritization Process, which is a democratic process where members of the Magento Open Source community can upvote the issues that they want to merge into the code base the most.

We added 10 pull requests to the community dashboard this month for processing, based on the votes on the PRs. Thank you to all the community members who voted!  

We added the following 10 pull requests to the community dashboard this month for processing, based on the votes on the PRs.

I’ve gotten some questions regarding the Community Prioritization Process.  It dawned on me that this might be a good chance to provide a reminder of what it is, what the goals are, and how each of you can contribute.

Community Prioritization Process Update – March 2023

On February 15-17, South Florida was the home of Meet Magento Florida 2023.  The Hard Rock Hotel was a great venue for a gathering of merchants, agencies, vendors, and developers.  I was impressed by the attendance and the enthusiasm and energy of the group.  There were speakers and attendees who had flown in from different parts of the world to make this a truly global event.  I was super excited to get a chance to meet new people, and reconnect with acquaintances I already knew.

I am happy to share the progress that we have made so far. We merged 6 pull requests this month and the batch includes one of the most loved pull request by the community – Allow more htmlClasses.  

I hope everyone had a great holiday season and ending to 2022.  I definitely took some time to rest and recharge, and am back excited about continuing to work with the community and deliver value for entrepreneurs and businesses with Magento Open Source.

The Magento Open Source Community Prioritization Process was kicked off in November of last year. This initiative empowers the community to influence the Magento Open Source roadmap and code base by upvoting the pull requests that brings most value to them. We then pick the most up voted PRs (Pull Requests) to work on and add them to the community dashboard with a purple label - “Community Picked.” 

We kicked off the Magento Open Source Community Prioritization Process last month. As part of this initiative, we have had community members use their influence to vote up certain pull requests they want to see incorporated into the Magento Open Source code base.  

I woke up this morning and wondered how the progress on community pull requests is going.  Yes, we implemented a process and asked the community to vote on the pull requests that they are most interested in merging, but now what?