Open Bug 1350081 Opened 3 years ago Updated 8 months ago

[meta] Create Bugzilla Extension for Privately Marking Bugs for Bookmarking

Categories

(bugzilla.mozilla.org :: General, task, P3)

Production

Tracking

()

People

(Reporter: emceeaich, Unassigned)

Details

(Keywords: bmo-big)

While votes are not used to determine what is worked on, some bugzilla users 'vote' bugs so they can bookmark them. Rather than overload the voting system, enable private bookmarking.
Isn't this covered by tagging bugs (which is off by default)?
(In reply to Sebastian Hengst [:aryx][:archaeopteryx] (needinfo on intermittent or backout) from comment #1)
> Isn't this covered by tagging bugs (which is off by default)?

I'm not sure. The tagging interface is hidden as you said (I could start covering it and do a quick intro) but it's not as simple as having 'bookmark this bug' button/link. 

It's also not clear how to search for tags. I don't see them in preferences > saved searches, or the dashboard, so we'd still have to expose UI for them, or surface UI that's hidden.
We actually discussed something similar a while back, turning voting into a favouriting-style feature: https://groups.google.com/d/topic/mozilla.dev.platform/uUQxA2_xjN4/discussion
(In reply to Sebastian Hengst [:aryx][:archaeopteryx] (needinfo on intermittent or backout) from comment #1)
> Isn't this covered by tagging bugs (which is off by default)?

The personal tagging feature of upstream is considered broken by the BMO maintainers (past and present).
It's off here, and I'd sooner remove it than use it for anything.
(In reply to Mark Côté [:mcote] from comment #3)
> We actually discussed something similar a while back, turning voting into a
> favouriting-style feature:
> https://groups.google.com/d/topic/mozilla.dev.platform/uUQxA2_xjN4/discussion

i had a write up of this with the proposal from the time, but i can't find it :(
so from memory..

our investigations revealed that voting was being used in multiple ways:

a) people outside of the project use it a a signal that they are impacted by the issue and assume their vote has a strong influence on a bug's priority
b) "personal bookmarking" as per comment 0.  "i'm interested in this bug and want to find it quickly in the future"
c) to follow the bug with the ability to treat emails differently from CCs.  this was surprisingly common - they wanted to know when a bug was fixed, but didn't want to receive notifications of every change to it.

our idea was to have single "favourite" button (eg. a star icon), with the following features:

- remove voting and bug tagging
  - migrate existing votes to favourites
  - migrate existing bug tags to vanilla saved queries
  - recommend users use browser bookmarks for bookmarking bugs
- notification option:
    - email me every change to my favourite bugs
    - email me when one of my favourite bugs changes status
    - do no email me about my favourite bugs
- page for listing and bulk editing your list of favourite bugs

if this is the route you want to take, it may be worth considering:

- change the 'follow' button's action from cc to favourite
- make searches based on favourite counts easier/trivial
- collect favourite counts over time and add to graphs / dashboard
(In reply to Byron Jones ‹:glob› from comment #5)
> (In reply to Mark Côté [:mcote] from comment #3)
> > We actually discussed something similar a while back, turning voting into a
> > favouriting-style feature:
> > https://groups.google.com/d/topic/mozilla.dev.platform/uUQxA2_xjN4/discussion
> 
> i had a write up of this with the proposal from the time, but i can't find
> it :(
> so from memory..
> 
> our investigations revealed that voting was being used in multiple ways:
> 
> a) people outside of the project use it a a signal that they are impacted by
> the issue and assume their vote has a strong influence on a bug's priority

Yes, because it has a number and "vote" instead of a collection, favorite or bookmarks.

> b) "personal bookmarking" as per comment 0.  "i'm interested in this bug and
> want to find it quickly in the future"

Yes, but it is not convenient for batch, because it is not an AJAX feature.

> c) to follow the bug with the ability to treat emails differently from CCs. 
> this was surprisingly common - they wanted to know when a bug was fixed, but
> didn't want to receive notifications of every change to it.

I often use it with a slightly different way, I usually want to get all changes but don't add to CC (trigger mail to reporter and history), I feel this may be an unnecessary harassment from my personal attention (probably an overly worry).

> our idea was to have single "favourite" button (eg. a star icon), with the
> following features:
> 
> - remove voting and bug tagging
>   - migrate existing votes to favourites
>   - migrate existing bug tags to vanilla saved queries
>   - recommend users use browser bookmarks for bookmarking bugs
> - notification option:
>     - email me every change to my favourite bugs
>     - email me when one of my favourite bugs changes status
>     - do no email me about my favourite bugs
> - page for listing and bulk editing your list of favourite bugs
> 
> if this is the route you want to take, it may be worth considering:
> 
> - change the 'follow' button's action from cc to favourite
> - make searches based on favourite counts easier/trivial
> - collect favourite counts over time and add to graphs / dashboard

I agree with these thoughts.
Type: enhancement → task
You need to log in before you can comment on or make changes to this bug.