Closed Bug 69784 Opened 25 years ago Closed 11 years ago

Personal Status Whiteboard

Categories

(Bugzilla :: Bugzilla-General, enhancement, P4)

enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: netdragon, Assigned: mail)

References

Details

Attachments

(1 file, 1 obsolete file)

There should be a personal status whiteboard for 3.0 that allows you to enter in whiteboard information for yourself as a bugzilla user. You could search for it just like other things. You would be able to put this on any bug. Other people wouldn't see this. ie: Personal Whiteboard: lame, dumb Personal Whiteboard: Its netdemon's birthday Personal Whiteboard: fixit
How far do you want to take this? The logical next step is group whiteboards, and how many do we want to create? For UI purposes it would need nice if u could "add" whiteboards.
Hixie, I think you already have this sort of thing in the BZ3 design, didn't you?
Assignee: tara → ian
Component: Bugzilla → Bugzilla 3
QA Contact: matty → ian
Target Milestone: --- → Bugzilla 3.0
that kind of thing (including group whiteboards) is already in the design, yeah. hell, you could even have personal drop downs and group cc lists and ... ;-)
Taking QA.
QA Contact: ian → matty
The Bugzilla 3 component is going away. We're going to depend on the Milestones for this. At the time this component was created, we didn't have milestones for Bugzilla.
Component: Bugzilla 3 → Bugzilla
Component: Bugzilla → Bugzilla-General
Priority: -- → P4
Product: Webtools → Bugzilla
Version: other → unspecified
Summary: [RFE] Personal Status Whiteboard → Personal Status Whiteboard
See also bug 167017, personal/group keywords.
Bailing on Bugzilla 3.0 due to too many other commitments.
Assignee: ian → nobody
Vlad's BugWrangler extension adds this feature to Firefox: http://www.vlad1.com/~vladimir/blog/archives/2004/07/28/39/
Assignee: nobody → nobody
(In reply to comment #8) > Vlad's BugWrangler extension adds this feature to Firefox: > http://www.vlad1.com/~vladimir/blog/archives/2004/07/28/39/ Vlad, can BugWrangler work on newer versions of FF, eg. DP? (right now, it doesn't)
It can't (and probably won't for a while) -- I tabled it because I couldn't get the functionality that I really wanted using RDF. Now that mozStorage is more stable and will be shipped as an extension at some point, bugwrangler might be reborn with a mozStorage dependancy for data storage.
QA Contact: mattyt-bugzilla → default-qa
This isn't actually going to be implemented in Bugzilla 3.0.
Target Milestone: Bugzilla 3.0 → ---
Assignee: nobody → general
I think this is basically the same I filed as bug 694555.
Assignee: general → bugzilla
Status: NEW → ASSIGNED
Attached patch bug69784-v1.patch (obsolete) — Splinter Review
Attachment #8638981 - Flags: review?(dylan)
Target Milestone: --- → Bugzilla 6.0
imho this should be configurable per site.
(In reply to Byron Jones ‹:glob› from comment #16) > imho this should be configurable per site. I think it should be a setting rather than in params.json, so individual users can turn it on or off, while allow administrators to turn it on or off globally if they wish. This differs from the status whiteboard, which is in params.json. Do you agree?
Flags: needinfo?(glob)
(In reply to Simon Green from comment #17) > I think it should be a setting rather than in params.json, so individual > users can turn it on or off It seems a bit weird to have a bug field hidden on a per-user basis. We never did that before, and I don't see the point to do that. It's like asking to not see bug aliases or the bug severity on a per-user basis. This would be totally confusing.
(In reply to Frédéric Buclin from comment #18) > It seems a bit weird to have a bug field hidden on a per-user basis. We > never did that before, and I don't see the point to do that. It's like > asking to not see bug aliases or the bug severity on a per-user basis. This > would be totally confusing. The difference between this field and alias and severity is that this is a field that is personal to the user (much like tags are). To that extent, you could argue that we don't have a per-user show tags option, so we shouldn't have one for personal whiteboard. OTOH, from a UI perspective, if only a few people want to use this feature, then why should we inflict another field on the majority of users that don't want this. Likewise, if this is on by default (which will be the default option), then a user can choose to remove seeing this field from the screen. Personally, I'm not fussed if it goes in the params file or settings, I just want a consensus on what is the best option in this case. My vote is for the settings for the reasons stated in the above paragraph.
(In reply to Simon Green from comment #17) > I think it should be a setting rather than in params.json, so individual > users can turn it on or off, while allow administrators to turn it on or off > globally if they wish. This differs from the status whiteboard, which is in > params.json. > > Do you agree? no, i think it should be controlled by the admin only, not users. after some thought i think this should be a bugzilla extension and not part of the core. it's an unusual request a decade old, with little interest until you wrote the patch. this gives the flexibility for sites that want to carry the overhead to install it, and for others that don't want this feature to not worry about it. > you could argue that we don't have a per-user show tags option, so we shouldn't have one for personal whiteboard. that we don't have the ability to disable bug tagging is bug 1116994.
Flags: needinfo?(glob)
Attachment #8638981 - Attachment is obsolete: true
Attachment #8638981 - Flags: review?(dylan)
Attachment #8639758 - Flags: review?(dylan)
(In reply to Byron Jones ‹:glob› from comment #20) > no, i think it should be controlled by the admin only, not users. Okay, I have added a new patch that includes a param for enabling it at the admin level. > after some thought i think this should be a bugzilla extension and not part > of the core. > it's an unusual request a decade old, with little interest until you wrote > the patch. > this gives the flexibility for sites that want to carry the overhead to > install it, and for others that don't want this feature to not worry about > it. I disagree. There is practically no overhead if this feature is not used (just an if statement here and there, and a few bytes for the table space). Having this as an extension would require a lot of work. I think these field is really useful, I know I would have used it a lot when I was a Bugzilla developer at Red Hat, just to write random notes, instead of using a notepad. Obviously, YMMV. In any case, if Dylan thinks it should be an extension, I'm sure he'll give it a big r-
Comment on attachment 8639758 [details] [diff] [review] bug69784-v1.patch Review of attachment 8639758 [details] [diff] [review]: ----------------------------------------------------------------- r- I don't think this belongs in Bugzilla.
Attachment #8639758 - Flags: review?(dylan) → review-
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Target Milestone: Bugzilla 6.0 → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: