canmove, Confirmed users
637
edits
BugzillaImprovements: Difference between revisions
→Make More Field Visibilities Configurable Per Product
(→Charts) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 13: | Line 13: | ||
* {{bug|373418}} | * {{bug|373418}} | ||
* Note that we are unlikely to add a user preference for this, but we might remember the shown/hidden state in a cookie. -mkanat | * Note that we are unlikely to add a user preference for this, but we might remember the shown/hidden state in a cookie. -mkanat | ||
Another option would be to have some of the key fields, plus the Commit button, as position:fixed at the top of the Window. This means that the general status of the bug is always visible, even if you visited a #comment-id link. And your muscle memory always knows where Commit is, as well. -- gerv | |||
=== Text Area Visible On Filing === | === Text Area Visible On Filing === | ||
| Line 88: | Line 90: | ||
Bug: too many to list. ;-) | Bug: too many to list. ;-) | ||
Repeating my (dveditz) earlier comment in the "historical data" section, the "new" charts need | |||
* the ability to make datasets public or shared with specific groups (like named queries). I mean user-created datasets, there do seem to be a few public ones I assume created by admins. | |||
* don't show 100's of datasets that the user isn't allowed to use. The clutter hides the ones I'm looking for, the interesting-looking names are a tease, and it's just overall frustrating. Just show me my own datasets, the public ones, and the ones that have been shared with me. | |||
** this one is [https://bugzilla.mozilla.org/show_bug.cgi?id=389396 bug 389396] | |||
=== Remove Severity Field === | === Remove Severity Field === | ||
| Line 115: | Line 122: | ||
No, it wouldn't, but it would require a fair bit of re-working that we're in-progress on, in terms of architecture, in Bugzilla. -mkanat | No, it wouldn't, but it would require a fair bit of re-working that we're in-progress on, in terms of architecture, in Bugzilla. -mkanat | ||
The ''presence'' of a field could be easily customized in each site's local CSS if we had a few tweaks to the bug layout: | |||
* each item must have an id. A lot of 'em do, but some the field itself has an id but its label does not, making it hard to style them as a group (e.g. target milestone and many others). | |||
* The body should have a product class in addition to the existing component class, that is "bz_product_Core" alongside "bz_component_JavaScript_Engine" <br>(dveditz) | |||
===Integrate Comments Into Bug History=== | ===Integrate Comments Into Bug History=== | ||
| Line 278: | Line 289: | ||
* Can't put an alias in a bookmarkable template. | * Can't put an alias in a bookmarkable template. | ||
* Add Core to the pretty picker {{bug|384603}} | |||
= Already Implemented = | = Already Implemented = | ||