| 2008-07-06 17:07:32 |
Matthew Paul Thomas |
bug |
|
|
added bug |
| 2008-07-17 20:03:41 |
Diogo Matsubara |
malone: status |
New |
Confirmed |
|
| 2008-10-21 14:56:00 |
Matthew Paul Thomas |
description |
Whenever you encounter a bug report page containing the message "This bug is not recorded as needing to be fixed in ______" and an "Also Needs Fixing Here" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Also Needs Fixing Here" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one.
So the only situation in which the "Also Needs Fixing Here" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Fixing this would resolve bug 45015 and bug 151251. |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one.
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Fixing this would resolve bug 45015 and bug 151251. |
|
| 2008-10-21 14:56:00 |
Matthew Paul Thomas |
title |
"Also Needs Fixing Here" is more harmful than useful |
"Yes, report it in ______" is more harmful than useful |
|
| 2008-10-24 10:59:16 |
Matthew Paul Thomas |
description |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one.
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Fixing this would resolve bug 45015 and bug 151251. |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one.
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Bug 287935 should be fixed at the same time as this bug. It may save time to fix bug 153763 at the same time as this bug. Fixing this bug would resolve bug 45015 and bug 151251. |
|
| 2008-11-24 22:27:16 |
Joey Stanford |
malone: status |
Confirmed |
New |
|
| 2008-11-24 22:27:16 |
Joey Stanford |
malone: importance |
Undecided |
Medium |
|
| 2008-11-24 22:27:16 |
Joey Stanford |
malone: statusexplanation |
|
I also agree as this has been confusing for a few people. I'm raising this to Medium and reseting to NEW so the bugs team triages this to their needs. |
|
| 2009-02-20 12:14:51 |
Matthew Paul Thomas |
description |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one.
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Bug 287935 should be fixed at the same time as this bug. It may save time to fix bug 153763 at the same time as this bug. Fixing this bug would resolve bug 45015 and bug 151251. |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one. (This was done by mistake, for example, in bug 331347.)
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Bug 287935 should be fixed at the same time as this bug. It may save time to fix bug 153763 at the same time as this bug. Fixing this bug would resolve bug 45015 and bug 151251. |
|
| 2009-02-20 16:34:33 |
Matthew Paul Thomas |
title |
"Yes, report it in ______" is more harmful than useful |
"Yes, report in ______" is more harmful than useful |
|
| 2009-02-20 16:36:05 |
Matthew Paul Thomas |
description |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one. (This was done by mistake, for example, in bug 331347.)
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Bug 287935 should be fixed at the same time as this bug. It may save time to fix bug 153763 at the same time as this bug. Fixing this bug would resolve bug 45015 and bug 151251. |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one. (This was done by mistake, for example, in bug 330143, bug 331311, and bug 331347.)
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Bug 287935 should be fixed at the same time as this bug. It may save time to fix bug 153763 at the same time as this bug. Fixing this bug would resolve bug 45015 and bug 151251. |
|
| 2009-03-25 11:40:13 |
Matthew Paul Thomas |
description |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one. (This was done by mistake, for example, in bug 330143, bug 331311, and bug 331347.)
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Bug 287935 should be fixed at the same time as this bug. It may save time to fix bug 153763 at the same time as this bug. Fixing this bug would resolve bug 45015 and bug 151251. |
Whenever you encounter a bug report page containing the message "This bug isn't linked to ______. Would you like to report it here as well?" and a miscapitalized "Yes, report in ______" button, ~99% of the time it is because the bug used to be filed on the context you're looking at it from, but has since been moved elsewhere. Even if that move was incorrect, clicking "Yes, report it in ______" is the wrong way to revert it, because it will add a new context to the bug report, rather than changing the existing one. (This was done by mistake, for example, in bug 330143, bug 331311, and bug 331347.)
So the only situation in which the "Yes, report it in ______" button is useful is if, knowing that a bug report is currently filed on one context but should also be filed on another, you manually construct the URL of the bug report in the as-yet-unfiled context, and visit it. This is so incredibly unlikely, that the button is clutter that is probably doing more harm than good.
I suggest that the button and its alert be removed, and that visiting a bug report in a context for which it is not filed should instead return a 301 Moved Permanently redirect to a context for which it is filed.
Bug 287935 should be fixed at the same time as this bug. It may save time to fix bug 153763 at the same time as this bug. Fixing this bug would resolve bug 45015, bug 151251, and bug 346876.. |
|
| 2009-04-21 10:39:16 |
Matt Zimmerman |
malone: status |
New |
Triaged |
|
| 2009-04-21 12:15:11 |
Björn Tillenius |
malone: milestone |
|
2.2.4 |
|
| 2009-04-23 09:48:59 |
Eleanor Berger |
malone: status |
Triaged |
In Progress |
|
| 2009-04-23 09:48:59 |
Eleanor Berger |
malone: assignee |
|
Tom Berger (intellectronica) |
|
| 2009-04-24 19:20:31 |
Diogo Matsubara |
malone: status |
In Progress |
Fix Committed |
|
| 2009-04-30 14:26:04 |
Björn Tillenius |
malone: status |
Fix Committed |
Fix Released |
|
