How do I: Bug tracking for Magento 1 + ideas for Magento 2

[seansan]

Hi, probably this is not the place. But - this is my/our best hint of getting an answer

** Where do I log bugs or ideas for Magento 1?
It seems the list http://www.magentocommerce.com/bug-tracking/list is dead. And nobody responds, .... so, where can we really contribute bugs or ideas for Magento 1?

** Then, many bugs or ideas also affect Magento 2 - where do I log those?
Many small configuration or operational issues that we see in Magento 1 we log at the above URL. But if nobody is watching this -> it will also never reach Magento 2 .... so, do I then log these more configuration settings/operational problems we see also here in github or where?

ps. If http://www.magentocommerce.com/bug-tracking/list is nog longer used. can someone then please just close it. I tink this is even better than creating an expectation

(sorry for those who are aggitated for me logging it here - but we love Magento and want to contribute)

[verklov]

@seansan, no worries about the question related to reporting Magento 1 bugs here. Let me respond to each of your bullet points.

Magento 1 bug tracking
The system we were using to track bugs in Magento 1 was not good for us due to the lack of integration with our internal bug tracker, which actually complicated the issues review process for us.

Our team is currently finalizing their efforts in the field and they promised to introduce the new system. I believe there will be a blog post or other announcement when the system will finally go live. So far cannot share any expectations on the system availability. We believe the new system will give us more possibilities on effectively tracking reported issues. Please stay tuned for the change.

Magento 2 bugs and ideas
For Magento 2 project we are using this GitHub repository. Please contribute everything that's on your mind here. We are watching all contributions.

You may see that plenty of ideas some of which are pretty old remain open in the GitHub. This is not an indication that we do not pay attention to them. We have our product backlog and all of the ideas and bugs are registered there. And we are trying to fit in bug fixes as priorities allow. Ideas are also validated and prioritized. Issues containing contributions that we think may be included into the code base will be closed in the repository once we process them. We just leave them open till that time to make sure people contributing their ideas are aware that there is such an idea and we know about it and considering it for including into Magento 2.

If you have an idea related to both Magento 1 and Magento 2, I would recommend that you contribute it to Magento 2 repository and to Magento 1 bug tracker once it is released.

Community members are those people that use our product and thus are able to notice things that we may see from a different angle. We are grateful for your help and precious ideas. We appreciate you contributing bug fixes and issues you encounter in the product. Unfortunately we are not always ready to accept all ideas for different reasons, but please continue helping us make Magento better.

[seansan]

Thank you for you marvellous answer

** For now: can you close the bug tracker then? this is creating the wrong expectations
http://www.magentocommerce.com/bug-tracking/list

** And my advice woul be to speed up the bug tracker for Magento 1.x ... or even as I suggested create a repository on github. Whihc is better indexed an where people can comment. No matter what system you choose to use later -> it can be exported anyways

** And my last addition would be => how does one then get bugs in het inbox of the Magento 1.x team?

Again many thanks for your answer

[verklov]

I will forward your recommendations on the Magento 1 bug tracker to the person in contact with the team working on this. We do hope they deliver it shortly - we in the Product team are also interested in having the system up and running the sooner the better.

The main point of contact for Magento 1 ideas is @piotrekkaminski. I hope he will be able to provide a recommendation on where to put bugs and requests for improvements till the time the new system is available.

@piotrekkaminski, could you share some ideas as for this question?

[piotrekkaminski]

Sure, we are moving to a bugtracker that is integrated with Jira - our internal system, so it's manageable. The old one was not integrated causing a lot of issues and lack of any feedback from our side. Github for 1.x is under consideration but the Github bugtracking is really hard to use for large amounts of reports. The easiest way to get to Magento 1.x team is to tweet me at @piotrekkaminski

[seansan]

@piotrekkaminski - I will send you some small stuff.

Please understand that I am gratefull that I can reach out

But sometimes I don't want want to bother directly - just record a small improvement here of there that make Magento better .... Small things .... and I know many people in our network here want to do this => we communicate about it a lot

And they are better recorded in a log then just send to you (because they disturb)

They are never urgent - but creative enough to be a real addition

Hope you make some progress with choosing/connecting the bugtracker.

Maybe we need something just to get started - for us now we feel there is nothing. Maybe the reports in Github are not the nest, but hey! you can paste screenshots, have ajax respons/reply, can reply by email, attach code, it is fast, can re-open and close, can assign to version, can branch ... so let's get it going

There is just so much we can do, can contribute, can improve, together

I hope you understand

For now I will ping you on Twitter

[seansan]

Hi guys,

just wondering how you are doing

"we are moving to a bugtracker that is integrated with Jira - our internal system, so it's manageable"

we have some small and simple ideas for Magento 1.x

how do we log them? and track them? or add code?

[benmarks]

@seansan http://www.magentocommerce.com/bug-tracking

[seansan]

I am sorry to respond/re-open to this again.

But in May we were moving to a bug tracker I understand from the above comment

I just logged a small improvement for CE 1.9.1 in the bugtracker. When I noticed 99% of all issues have the status "open" and don't seem to be touched

My question:
** are these issues being welcomed by the team? (and how can we know)

** do you advise me to separately log these issues for Magento 2?

[seansan]

@verklov @piotrekkaminski May I respond to your comment in May 2014

"Our team is currently finalizing their efforts in the field and they promised to introduce the new system. I believe there will be a blog post or other announcement when the system will finally go live. "

When I look @ http://www.magentocommerce.com/bug-tracking/list/index/page/10 => even months back all bugs have the status open.

Why not move Magento 1.9.x to a public github repository too? I don't understand why one would have a github repo and the other not ...

I think my question remains open: how and where can we log issues and suggest pull requests to the code directly to help fix issues? Where one can comment and collaborate?

I hope it helps

thanks guys!

[magento-engcom-team]

Hi @seansan. Thank you for your report.
The issue has been fixed in #25349 by @konarshankar07 in 2.4-develop branch
Related commit(s):

• a4a2ff7d2444fe24bf13f022b9748ddb961a095c
• c42d48a44829ad91024e2c61f14fa9d5e9fe9731
• b8e0c42cba3db9a4b5005fe7e0d078891ad5b0ce
• d6995f7595363e896415f06c1228ffc2f2f719ff
• c9f9757fe815ac1e390b9943df5c5a046eb62491
• 240fc19617589cecc528799824ad1b8378558dd4
• da6b3612ff51e52caf4bcf7dccf7690cd79d9cd4
• db51191275245123b84d772a80820454a2cb5631
• 3e25bd1385e9287f0ba5d5c6579a2f65ade3d2b4
• 633ea172803d6d81b823f8791226bf1d0e516957
• 5d676b60bbcc8a03fe50bc417c5f17b7e62a99d3
• 997959f2f081f844b798ccae31cc54fa0833ca60
• d3aa9320e82eb9f1f6ee903c1bef0dd4e2983b3e
• 65b2afeeea0801291a924eb64618650faa8d2e93
• 727679d3c9ee2540cb707fe1431d25b7fbae7a34
• b41ea13a925eda843277dc9960071f00207b329e
• 552eaafd5029a982c5243670e71d618467602319
• ce6614ef0e813e2d2ae8226c715d8d0a5cfb4d1a
• c14fbedfac2559ae05767e98afcd7d274ec5da48
• 257eb00a4400dbddf7e0a6774fc927eb198d8381
• b1ab6a97c8354b3ef1c80aac379140fe356898e4
• 53fe8eecbd87c7a0e3924e81cd9d77e9300eb9d4
• 437fab3b783eb68460d283214f41f6b9d9fcb49f

The fix will be available with the upcoming 2.4.0 release.