Skip to content

Can Someone Explain How This Bug Reporting Process On Github Is Supposed to Work? #4082

@ghost

Description

At the bottom of every Magento 2.0.x admin page there's a link 'Report Bugs' which brings you to https://github.com/magento/magento2/issues/ (this page).

Because of that I would expect that this github page is the authoritative place to report bugs, correct?

Given that, I would also expect that there'd be some underlying process to progress the reports, correct?

What are the different steps along the way from 'opened' to 'closed'? I'm asking this because I see many issues that been lying fallow for many, many days.

Now I fully appreciate that there are a significant number of open issues (1153 at writing), and that a lot of those may have been very poorly written up and have had no follow-up from the submitter when additional info is requested. I also see that there are hundreds that appear to have zero comments ... which indicates that they are getting zero attention. Why are they sitting around looking like litter?

All this makes clicking on "Report Bugs" almost worthless. :(

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions