GitHub Issue Priority

maxyek · ‎02-07-2017

One of the privileges of running an open source software project is having direct and open interaction with our users. We've relied on GitHub as the major medium for this interaction for well over two years. Recent developer experience initiatives, such as Magento DevBox and the Community Engineering charter, are designed to broaden and better facilitate our interaction with the community going forward. This is the first of several posts which provide more detail about individual improvements.

GitHub's issues list offers a place to report and discuss potential issues. Our core team checks to see if submitted Magento 2 issues can be reproduced and are not duplicates. Confirmed issues are then prioritized to be fixed and eventually released.

As I shared at MagentoLive France this morning, our community is now able to help us prioritize issues through the use of GitHub's "Reactions" feature: thumbs-up is a vote for prioritizing an issue, and thumbs-down is a vote against prioritizing it. We will use these votes to help us order issues for resolution, which means that our community has a greater ability to influence what our core team is working on. Issues most important to our users will be more likely to be resolved and released sooner.

As a reminder, feature requests should be directed to, and upvoted at, the feature request subforum.

This is one of many enhancements to our community collaboration. We look forward to your contributions and feedback to help us prioritize the issues that matter to you. If you have any questions, please comment below.

erikpallha · ‎02-07-2017

I love this idea. One thing you may want to clarify in your post: will you only count thumbs up/down reactions on the original issue, or any of the comments on the issue?

maxyek · ‎02-08-2017

Hi @erikpallha, we are using standard sorting feature of GitHub, and it uses thumb-ups in original issue only, ignoring thumb-up on comments.

baldwin_pieter · ‎02-11-2017

Great job @maxyek, good to see that there are improvements being made to addressing Github issues more quicker.

A question: does upvoting a closed issue also help for you? Because there are a lot of issues closed because there is a fixed delivered on the develop branch, but which haven't been backported to 2.0.x or 2.1.x, so I'm not sure if you are also watching closed issues? So how can we try to upvote issues which should get backported?

Also: it feels like you are completely ignoring closed tickets, whenever a comment is added to one asking the help from the Magento support people for example. If we want to draw your attention to a closed issue, how do we do that? Should we open a new issue with a reference to the closed one?

Please forgive me, if this is not the appropriate place to post this, but below is a list of issues I compiled by searching through the comments of some of our own projects, and these are all the issues we currently run into, for most of them, we have figured out a workaround, or apply patches directly from commits on github which we tried to backport ourselves. Maybe this also helps in prioritizing issues. This is very biased towards our own needs, and not to the community needs, so if this doesn't fit here, let me know and I'll remove the list.

Fixed on develop, but not backported to 2.1.x

Looks like it is already fixed in 2.1.x, but hasn't been confirmed yet

- https://github.com/magento/magento2/issues/6984 (MAGETWO-58977)

Open issues which haven't been addressed yet

Incorrectly closed issues which should be reopened (in my opinion)

- https://github.com/magento/magento2/issues/5262 (MAGETWO-52095)
- https://github.com/magento/magento2/issues/6325
- https://github.com/magento/magento2/issues/6638

maxyek · ‎02-16-2017

Hi @baldwin_pieter,

Thank you very much for questions and analysys you made on github issues. There is no solid answer on your questions, yet! And my goal to get the answers together with community.

In terms of upvoting on closed issues - at the moment we are not monitoring (or rarely monitoring such issues), due overload on opened issues. In terms of attention - feel free to add me in comments on closed issues, or/and ping in twitter, slack e.t.c. I will review and provide justification if needed or reopen in case it valid case.

We are not backporing all issues, but only one which will have majority votes, with request to backport. We are focusing majority our workforce on upcoming 2.2 release, and it is main reason why we want to backport only issues which community voted most.

jmtakahashi · ‎03-01-2017

@maxyekplease consider re-opening this issue regarding 2.1.X and the basic Catalog Price Rule problem for people running not-so-complex stores. There are several issues that seem to revolve around this issue and it seems intuitive for a basic function like this to work properly.

https://github.com/magento/magento2/issues/7093

Also, with the new release of 2.2 is this is "new features" release or a release that focuses on fixing bugs. Per Alan Kent's post earlier this year I thought Magento was focusing on bug fixes over new features, as there are so many bugs to get worked out before new bugs (aka features) are released.

DSS Rashid · ‎05-03-2017

This issue is pending kindy check

https://github.com/magento/magento2/issues/9226