[BUGTRACKER] Migrate from Monorail to something else
Reported by
teo8...@gmail.com,
Mar 2 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Steps to reproduce the problem: Monorail is the most shitty bugtracker I've ever had to deal with. Reporting its bugs is a waste of time, given that most other popular bug trackers are not affected by the thousands of bugs that make monorail so shitty. Instead of having us waste our time reporting bugs to monorail, why don't you just migrate to a decent bugtracker that already exists?? What is the expected behavior? What went wrong? Monorail is the most shitty bugtracker I've ever had to deal with. Reporting its bugs is a waste of time, given that most other popular bug trackers are not affected by the thousands of bugs that make monorail so shitty. Instead of having us waste our time reporting bugs to monorail, why don't you just migrate to a decent bugtracker that already exists?? Did this work before? No Chrome version: 48.0.2564.116 Channel: n/a OS Version: Flash Version: Shockwave Flash 20.0 r0
,
Mar 24 2016
I'm sure the monorail team will be happy to fix issues. Please log monorail issues here: https://bugs.chromium.org/p/monorail |
||
►
Sign in to add a comment |
||
Comment 1 by kavvaru@chromium.org
, Mar 3 2016Labels: Needs-Feedback