Dietrich Ayala (:dietrich) Reporter
	Description • 11 years ago

We currently track activity via product/component combinations. However, across the many many teams working on Firefox OS (both inside and out of MoCo) the querying using only product/component gives a view too blurry to be helpful.

* components are not strictly divided between teams

* activity happens across many products

* inability to by discrete groups of *users* hampers visibility into team-wide activity, over/under-loading and other activity patterns (regressions, performance, etc)

Note: Yes, we could hand-craft searches with the members of each team, but the cost of doing that becomes high with so many people. If users could just put their team in their account into and we can query on that, it becomes much easier to manage across so many teams. It also allows external groups (academic groups, various partners) to be represented and tracked.

	:glob ✱
	Comment 1 • 11 years ago

this was discussed in our bmo team meeting and it was agreed that this would be a valuable enhancement and that allowing users to add tags to their own profile would be a good way to achieve this.

while this isn't a q2 goal for us, it's something we hope to be able to deliver before the end of q2.



initial thoughts on implementation:
- borrow the schema and tagging ui from comment tags
- allow tags to be added via user preferences and the user profile pages
- add four new search operators:  tagany, tagall, nottagany, nottagall (tag-any, tag-all, not-*)
  - only applicable to user fields (maybe extend to comments and bugs if time allows)
  - add operators to the 'search by people' operator selects on the advanced search page
  - add to list/list.html.tmpl, search/boolean-chart.html.tmpl, and field-desc.none.tmpl
- add as a column to buglist results
  - limited to primary actors only: reporter-tags, assignee-tags, maybe qa-contact-tags
  - use sql_group_concat to build a comma separated list
- add to webservice responses for users
- i'm not sure about how user tags should be displayed on show_bug, if at all.  i'm currently leading towards "don't display".  if we do display user tags on show_bug, it should be for the primary actors only (not every commenter).