Closed
Bug 705051
Opened 13 years ago
Closed 13 years ago
enter_bug.cgi should say if a product is visible only to people with permissions
Categories
(bugzilla.mozilla.org :: User Interface, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dbaron, Assigned: gerv)
Details
Attachments
(2 files, 3 obsolete files)
2.28 KB,
patch
|
Details | Diff | Splinter Review | |
1.50 KB,
patch
|
gerv
:
review+
|
Details | Diff | Splinter Review |
https://bugzilla.mozilla.org/enter_bug.cgi?full=1 lists the products available to the bug reporter. However, sometimes the bug reporter can see products that others can't. But this can lead to confusion when talking about how to file a bug. See, for example: https://groups.google.com/group/mozilla.governance/msg/b368329baf156921 For example, one of the products in b.m.o, "Mozilla Corporation" (which is for filing bugs on the office, like if there's a problem with the plumbing), is visible only to people who have the MoCo-employee permission bit set on their account. To avoid this, enter_bug.cgi should have text (and probably also a different background color) next to a product that's only visible to some users saying who it's visible to.
Updated•13 years ago
|
Severity: normal → enhancement
OS: Linux → All
Hardware: x86_64 → All
Comment 1•13 years ago
|
||
Probably just displaying the lock icon would do.
Some bugzillas restrict all products. You might get away with a lock icon on bmo, but it's useless and won't help anyone. The question someone needs to answer is "what group do I need to be in to use this product/component?"
Assignee | ||
Comment 3•13 years ago
|
||
The Bugzillas which restrict all products are being used in a different way to public Bugzillas which have some restrictions. There are various places where the best UI for the two has to differ, and this is one of them. It's fine for the actual UI for this to be a bmo-only change, although the infrastructure (e.g. CSS classes) to support it should be upstreamed. Each "row" should have a CSS class "group" if it's in any group, and then "group-N" for each group you need to be/can be in. Gerv
Comment 4•13 years ago
|
||
I'm fine with a lock icon for now. We already have it and it will be easy to implement.
Assignee | ||
Comment 5•13 years ago
|
||
WIP patch. But I can't quite figure out how to ask a Product object for a list of all the groups you need to enter a bug into it... dkl, any ideas? Gerv
Comment 6•13 years ago
|
||
You can use Bugzilla::Product::group_controls to get the information you need. I have created a patch that shows how to use it in enter_bug.cgi. Just need the related CSS changes to display the secure icon. dkl
Assignee | ||
Comment 7•13 years ago
|
||
dkl: Great! One issue: this patch leaks group names; I believe we have a policy of not leaking group names to people not in the relevant group? Replace ".name" with ".id" and it should be OK. Updated patch attached with CSS - is it in the right place? Gerv
Attachment #581632 -
Attachment is obsolete: true
Attachment #581878 -
Attachment is obsolete: true
Attachment #581632 -
Flags: review?(dkl)
Attachment #581955 -
Flags: review?(dkl)
Comment 8•13 years ago
|
||
Lets do this. Since this is patching file(s) that are part of the BMO extension for now, we will track this as a BMO customization. The once complete, Gerv can work up a patch that works with the upstream code and create a new bug for review separate from this one. dkl
Component: Creating/Changing Bugs → User Interface
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa → ui
Version: unspecified → Current
Comment 9•13 years ago
|
||
Comment on attachment 581955 [details] [diff] [review] Patch v.2 Review of attachment 581955 [details] [diff] [review]: ----------------------------------------------------------------- I would move the change in skins/standard/global.css to skins/custom/global.css since this will initially be a BMO only change. Later if accepted upstream it will go into skins/standard/global.css. Also I would add a title= attribute to the <a> product link and/or the icon image stating that the product is protected by one or more permission groups just for further clarity if entry_groups.size > 0. dkl ::: skins/standard/global.css @@ +575,5 @@ > #down_button { > background-image: url(global/down.png); > } > + > +.group_secure > th { Currently the lock shows up on the far left of the window on the same row as the product leaving a gap. I feel it would be less confusing if the icon was right next to the link itself. So changing to: .group_secure > th > a { accomplishes that.
Attachment #581955 -
Flags: review?(dkl) → review-
Assignee | ||
Comment 10•13 years ago
|
||
Attachment #581955 -
Attachment is obsolete: true
Attachment #582285 -
Flags: review?(dkl)
Comment 11•13 years ago
|
||
Look at this more, I think this patch simplifies it and also cuts out an extra loop. Your patch is fine too but let me know if you think this way is better. dkl
Attachment #582381 -
Flags: review?(gerv)
Assignee | ||
Comment 12•13 years ago
|
||
Comment on attachment 582381 [details] [diff] [review] Patch (dkl) Yep; I must have lost the wood in the trees. Seems fine. Gerv
Attachment #582381 -
Flags: review?(gerv) → review+
Comment 13•13 years ago
|
||
Thanks gerv Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.0 modified extensions/BMO/template/en/default/global/choose-product.html.tmpl modified skins/custom/global.css Committed revision 7987 dkl
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Attachment #582285 -
Flags: review?(dkl)
You need to log in
before you can comment on or make changes to this bug.
Description
•