51100 - Configurable "home page" per engineer and per team

Status: RESOLVED DUPLICATE of bug 130835

(Bugzilla :: User Interface, enhancement)

Description

[selmer (gone)]

In our life cycle, we go through a lot of phases where we change the goals from
the just-previous phase.  These goals usually end up being expressible in bug
query form.  It would be a big productivity boost if engineers could ask
bugzilla to "just show me what's important today" without having to invent a set
of queries on their own.  The main thing about this is that the engineers aren't
determining what's important, but their the only ones who can make it really happen.

The system I'm envisioning would allow the manager to submit a template and some
query strings that each member of his/her team would see whenever they went to
their bugzilla home page.  By updating the template or the queries, the manager
can start to have confidence in the mind share with the developers on the
current goals.

It would also be very handy to be able to do this for teams so that the queries
of interest to the team and its partners are always easily accessible and
annotated by the template.

I think this could be a boon to the open source effort since it'll create a
pretty simple mechanism for disseminating vital information and help keep a
diverse and widespread team all on the same page.  (pun intended :-)

Comment 1

[Dave Miller [:justdave]]

I'd been toying with the idea of trying to turn the index page into a .cgi for 
quite some time for a number of reasons:

a) you could have the site's PutHeader() routine automatically used, so you 
didn't have to manually add it to your index.html file

b) The index page could do things that depended on knowing who the user was 
(like having the proper commands in PutFooter(), which could also be used 
because of this).

c) your idea here is another good example of the possibilities.

The templates would need to be generic enough that they can be combined if a 
person is a member of more than one group, or displayed in sections, with a 
section for each group they belong to.

With an organization the size of mozilla.org, I can easily see this using up 
more than the 64 groups bugzilla has available for grouping people like this.  
Not to mention that those groups are mostly used for access to things, and I 
think it would be appropriate to be able to make groups of people who wouldn't 
necessarily have different access from each other.  So I'm marking this as 
dependent on the bug 51099 that you submitted requesting a way to look up people 
by a group alias.

Comment 2

[selmer (gone)]

It would be very cool if the home page showed bugs recently filed by this person.

Comment 3

[Dave Miller [:justdave]]

-> Bugzilla product

Comment 4

[Dave Miller [:justdave]]

The User Interface component now belongs to Gerv.  Reassigning all UNCONFIRMED
and NEW (but not ASSIGNED) bugs currently owned by Myk (the previous component
owner) to Gerv.

Comment 5

[Dave Miller [:justdave]]

Reassigning back to Myk.  That stuff about Gerv taking over the User Interface
component turned out to be short-lived.  Please pardon our confusion, and I'm
very sorry about the spam.

Comment 6

[Myk Melez [:myk] [@mykmelez]]

Removing 51099 dependency, since that can be done without this bug.  Adding
dependency on bug 130835, since any group- or user-specific index page is going
to have to take that rewrite into account.  I'd like to see some degree of
customizability of the home page, although I'm not sure exactly how to approach
it.  Is anyone else still interested in this bug?

Comment 7

[selmer (gone)]

I am definitely still interested in this, although I've just about given up hope
of seeing it implemented.

I wouldn't use the existing grouping mechanism for this.  It'd be easier to use
a cookie on the client saying which home page view(s) they want to see.  I also
wouldn't start off by implementing a mechanism to merge views.  I'd rather see
something useful show up soon than see something fancy maybe show up later.

Comment 8

[Arne Schirmacher]

I'm interested too. I have written a new cgi page (bug #203709) where a user is
presented lists of his assigned bugs, issues to retest etc. 

It is not configurable, but it is simple and works for me.

Comment 9

[:glob ✱]

*** Bug 299690 has been marked as a duplicate of this bug. ***

Comment 10

[Frédéric Buclin]

(In reply to comment #6)
> Is anyone else still interested in this bug?

I could take it for 2.24... I was thinking about something similar to bug 203709 (not exactly the same thing, but close).

Comment 11

[Frédéric Buclin]

This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".