New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 591367 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

[BUGTRACKER] Migrate from Monorail to something else

Reported by teo8...@gmail.com, Mar 2 2016

Issue description

UserAgent: 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
 
Cc: kavvaru@chromium.org
Labels: Needs-Feedback
teo8976@ Thanks for the issue.

Could you please provide us the exact issue and expected behavior to triage the issue further.

Thanks,
Cc: dtapu...@chromium.org
Status: WontFix (was: Unconfirmed)
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