Magento 2 Open Source – How to investigate outstanding issues

A little history

It’s been a long time since I delved into Magento 2 development – I gave up in 2017 when the 2.1 release was riddled with issues. The company I work for had to do an emergency reversion back to Magento 1 (they moved from Magento 1 Enterprise > Magento 2 CE > Magento 1 CE).

We had two agencies at the time trying to resolve the issue, the dreaded checkout problem: “An error occurred on the server. Please try to place the order again”. Granted my general feeling was that not many agencies, developers or plugin creators had extensive experience with Magento 2.

Magento 1 EOL – June 2020

Magento announced in September 2018 that Magento 1 was coming to EOL in June 2020. This was a relief for many merchants because back then, they had similar complaints of Magento 2. It didn’t work or developers were migrating (very poorly) their plugins and themes.

Revisiting Magento 2.3

It’s only natural for merchants to move across to Magento 2 but before you do, make sure you check what the current open issues are – and try to figure out if any of these issues may impact your store (i.e. for example you may be using a feature that has a problem).

There are two places I would recommend you visit to get an idea of the status and stability of Magento:

  1. Magento’s component status page
  2. Magentos github page

Magento’s component status page

Buried within the documentation is a page which lists the individual status of each “plugin/component” bundled with Magento 2.3:

On this page is a traffic light system to denote the status:

Magento 2 Component Status

You probably won’t find an Red¬†statuses in the official release as that would deem the release unfit. You will see Yellow instances lurking about, for example currently (as of 25.02.2019) there some minor issues with Checkout:

magento 2.3 checkout issue status page

Unfortunately this page does not provide further information – this is where Github comes in.

Magento’s Github page

Head over to the official Magento Open Source repository on Github: Within that you can check what the current issues are by clicking on the Issues tab:

How to Check Magento 2 open coding issues

This will load the page with all the ‘open’ issues:

Magento 2 Git Codebase open issues

This may appear a little daunting but this by default is showing all the open issues for all the different versions of Magento.

You may have noticed the following search bar:

Here you can enter keywords or you can go a bit more advanced by searching through the “Labels”:

github label dropdown

You can start typing some keywords. For example I am interested in seeing all the Magento 2.3 issues, so I start to type 2.3 and select “Reproduced on 2.3.x“:

Github search magento release line

We also want to find¬† out what the current “checkout” issues are. Head over to the Label drop down and enter “Checkout” into search and select Component: Checkout.

component checkout issue

And your results should show all the:

  • Open issues
  • Reproduced on 2.3.x
  • Component: Checkout


Whilst seeing all the open issues may be daunting – if you read into the details you will either find they are are not severe or there is a temporary fix/patch available by somebody in the community.

For more information about applying a patch you find on Github, check out this cool post by Mark Hurst:

Featured image – ‘binoculars’ graphic created by

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.