We need a complete UX overhaul here. A plain HTML `<input>` element worked when we only had a few thousand of bugs, but the world has changed as Mozilla and Red Hat now have 7-digit bugs. Editing `<input>` with dozens of bugs is really painful. Also, we’ll soon have 4 and eventually 6 fields accepting multiple bug IDs: * Depends on * Blocks * Regressions (to be added soon in Bug 1461492) * Regressed by (same) * See Also (currently both bug IDs and URLs are accepted but [this will change](https://bugzilla.mozilla.org/show_bug.cgi?id=577847#c21)) * Duplicates (currently read-only but should be editable) What we need: * Text field with autocomplete * Accepts both ID and alias * When a bug is selected from the dropdown, it will added to the bug list * Bug list: each bug will look like a label, which * Shows not only with ID or alias but also summary + [type](https://bugzilla.mozilla.org/show_bug.cgi?id=1527459) * Some people are doing this with a user script * Provides a remove button like the current CC list * Supports drag & drop so you can move a bug to another field * Shows a [hovercard](https://bugzilla.mozilla.org/show_bug.cgi?id=1146763) Having a [2-column layout](https://bugzilla.mozilla.org/show_bug.cgi?id=1330451) will make it easier to implement these changes.
Bug 1539271 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We need a complete UX overhaul here. A plain HTML `<input>` element worked when we only had a few thousand of bugs, but the world has changed as Mozilla and Red Hat now have 7-digit bugs. Editing `<input>` with dozens of bugs is really painful. Also, we’ll soon have 4 and eventually 6 fields accepting multiple bug IDs: * Depends on * Blocks * Regressions (to be added soon in Bug 1461492) * Regressed by (same; usually only have 1 bug) * See Also (currently both bug IDs and URLs are accepted but [this will change](https://bugzilla.mozilla.org/show_bug.cgi?id=577847#c21)) * Duplicates (currently read-only but should be editable) What we need: * Text field with autocomplete * Accepts both ID and alias * When a bug is selected from the dropdown, it will added to the bug list * Bug list: each bug will look like a label, which * Shows not only with ID or alias but also summary + [type](https://bugzilla.mozilla.org/show_bug.cgi?id=1527459) * Some people are doing this with a user script * Provides a remove button like the current CC list * Supports drag & drop so you can move a bug to another field * Shows a [hovercard](https://bugzilla.mozilla.org/show_bug.cgi?id=1146763) Having a [2-column layout](https://bugzilla.mozilla.org/show_bug.cgi?id=1330451) will make it easier to implement these changes.
We need a complete UX overhaul here. A plain HTML `<input>` element worked when we only had a few thousand of bugs, but the world has changed as Mozilla and Red Hat now have 7-digit bugs. Editing `<input>` with dozens of bugs is really painful. Also, we’ll soon have 4 and eventually 6 fields accepting multiple bug IDs: * Depends on * Blocks * Regressions (to be added soon in Bug 1461492) * Regressed by (same; usually only have 1 bug) * See Also (currently both bug IDs and URLs are accepted but [this will change](https://bugzilla.mozilla.org/show_bug.cgi?id=577847#c21)) * Duplicates (currently read-only but [should be editable](https://bugzilla.mozilla.org/show_bug.cgi?id=1539277)) What we need: * Text field with autocomplete * Accepts both ID and alias * When a bug is selected from the dropdown, it will added to the bug list * Bug list: each bug will look like a label, which * Shows not only with ID or alias but also summary + [type](https://bugzilla.mozilla.org/show_bug.cgi?id=1527459) * Some people are doing this with a user script * Provides a remove button like the current CC list * Supports drag & drop so you can move a bug to another field * Shows a [hovercard](https://bugzilla.mozilla.org/show_bug.cgi?id=1146763) Having a [2-column layout](https://bugzilla.mozilla.org/show_bug.cgi?id=1330451) will make it easier to implement these changes.
We need a complete UX overhaul here. A plain HTML `<input>` element worked when we only had a few thousand of bugs, but the world has changed as Mozilla and Red Hat now have 7-digit bugs. Editing `<input>` with dozens of bugs is really painful. Also, we’ll soon have 4 and eventually 6 fields accepting multiple bug IDs: * Depends on * Blocks * Regressions (to be added soon in Bug 1461492) * Regressed by (same; usually only have 1 bug) * See Also (currently both bug IDs and URLs are accepted but [this will change](https://bugzilla.mozilla.org/show_bug.cgi?id=577847#c21)) * Duplicates (currently read-only but [should be editable](https://bugzilla.mozilla.org/show_bug.cgi?id=1539277)) What we need: * Text field with autocomplete * Accepts both ID and alias * When a bug is selected from the dropdown, it will be added to the bug list (and hidden `<input>`) * Bug list: each bug will look like a label, which * Shows not only with ID or alias but also summary + [type](https://bugzilla.mozilla.org/show_bug.cgi?id=1527459) * Some people are doing this with a user script * Provides a remove button like the current CC list * Supports drag & drop so you can move a bug to another field * Shows a [hovercard](https://bugzilla.mozilla.org/show_bug.cgi?id=1146763) Having a [2-column layout](https://bugzilla.mozilla.org/show_bug.cgi?id=1330451) will make it easier to implement these changes.
We need a complete UX overhaul here. A plain HTML `<input>` element worked when we only had a few thousand of bugs, but the world has changed as Mozilla and Red Hat now have 7-digit bugs. Editing `<input>` with dozens of bugs is really painful. Also, we’ll soon have 4 and eventually 6 fields accepting multiple bug IDs: * Depends on * Blocks * Regressions (to be added soon in Bug 1461492) * Regressed by (same; usually only have 1 bug) * See Also (currently both bug IDs and URLs are accepted but [this will change](https://bugzilla.mozilla.org/show_bug.cgi?id=577847#c21)) * Duplicates (currently read-only but [should be editable](https://bugzilla.mozilla.org/show_bug.cgi?id=1539277)) What we need: * Text field with autocomplete * Accepts both ID and alias * Also searches against the user’s recently visited bugs * When a bug is selected from the dropdown, it will be added to the bug list (and hidden `<input>`) * Bug list: each bug will look like a label, which * Shows not only with ID or alias but also summary + [type](https://bugzilla.mozilla.org/show_bug.cgi?id=1527459) * Some people are doing this with a user script * Provides a remove button like the current CC list * Supports drag & drop so you can move a bug to another field * Shows a [hovercard](https://bugzilla.mozilla.org/show_bug.cgi?id=1146763) Having a [2-column layout](https://bugzilla.mozilla.org/show_bug.cgi?id=1330451) will make it easier to implement these changes.
We need a complete UX overhaul here. A plain HTML `<input>` element worked when we only had a few thousand of bugs, but the world has changed as Mozilla and Red Hat now have 7-digit bugs. Editing `<input>` with dozens of bugs is really painful. Also, we’ll soon have 4 and eventually 6 fields accepting multiple bug IDs: * Depends on * Blocks * Regressions (to be added soon in Bug 1461492) * Regressed by (same; usually only have 1 bug) * See Also (currently both bug IDs and URLs are accepted but [this will change](https://bugzilla.mozilla.org/show_bug.cgi?id=577847#c21)) * Duplicates (currently read-only but [should be editable](https://bugzilla.mozilla.org/show_bug.cgi?id=1539277)) What we need: * Text field with autocomplete * Accepts both ID and alias * Also searches against the user’s recently visited bugs * Do sanity check client side: e.g. the same bug cannot be added to both the Depends on and Blocks fields * When a bug is selected from the dropdown, it will be added to the bug list (and hidden `<input>`) * Bug list: each bug will look like a label, which * Shows not only with ID or alias but also summary + [type](https://bugzilla.mozilla.org/show_bug.cgi?id=1527459) * Some people are doing this with a user script * Provides a remove button like the current CC list * Supports drag & drop so you can move a bug to another field * Shows a [hovercard](https://bugzilla.mozilla.org/show_bug.cgi?id=1146763) Having a [2-column layout](https://bugzilla.mozilla.org/show_bug.cgi?id=1330451) will make it easier to implement these changes.
We need a complete UX overhaul here. A plain HTML `<input>` element worked when we only had a few thousand of bugs, but the world has changed as Mozilla and Red Hat now have 7-digit bugs. Editing `<input>` with dozens of bugs is really painful. Also, we’ll soon have 4 and eventually 6 fields accepting multiple bug IDs: * Depends on * Blocks * Regressions (to be added soon in Bug 1461492) * Regressed by (same; usually only have 1 bug) * See Also (currently both bug IDs and URLs are accepted but [this will change](https://bugzilla.mozilla.org/show_bug.cgi?id=577847#c21)) * Duplicates (currently read-only but [should be editable](https://bugzilla.mozilla.org/show_bug.cgi?id=1539277)) What we need: * Text field with autocomplete * Accepts both ID and alias * Also searches against the user’s recently visited bugs * Do sanity check client side: e.g. the same bug cannot be added to both the Depends on and Blocks fields * When a bug is selected from the dropdown, it will be added to the bug list (and hidden `<input>`) * Bug list: each bug will look like a label, which * Shows not only with ID or alias but also summary + [type](https://bugzilla.mozilla.org/show_bug.cgi?id=1527459) * Some people are doing this with a user script or stylesheet * Provides a remove button like the current CC list * Supports drag & drop so you can move a bug to another field * Shows a [hovercard](https://bugzilla.mozilla.org/show_bug.cgi?id=1146763) Having a [2-column layout](https://bugzilla.mozilla.org/show_bug.cgi?id=1330451) will make it easier to implement these changes.