Closed Bug 1173873 Opened 9 years ago Closed 5 years ago

"Number of Reps per country" view

Categories

(Mozilla Reps Graveyard :: reps.mozilla.org, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mkohler, Assigned: mkohler)

Details

(Whiteboard: [profiles][next])

After a discussion on Telegram, I'm filling this bug now. Some of us think that it would be great to have a view where you see the number of Reps per country. I know that this can't be used as a KPI, but it would still be quite interesting.

In my mind that would be a list of all the countries with the number of Reps being from this country. This could be either sorted alphabetically by country name or by number of Reps. I think this should be decided before starting to work on this.

How much of work would that be? Do you think this is something we should do?
Group: mozilla-reps-admins
@mkohler: sounds like a fun idea! On the technical side, it wouldn't be hard to implement this. Adding a needinfo for :nukeador to evaluate if this is something that we should proceed with and if yes to kick start the discussion on implementation details.
Flags: needinfo?(nukeador)
Yes, we should re-start the conversations about improvements on the KPI dashboard.
Flags: needinfo?(nukeador)
Hey all!

Currently there is a way to extract such data. You can export all reps from People view and create a Pivot table for countries. Obviously not optimal but the data is publicly available.

Trying to dig into the real need behind this I was thinking whether a cluster map would be more optimal as a solution (for all our map views)

Check bug 1180649 for details and let me know!
Priority: -- → P2
Whiteboard: [profiles]
Assignee: nobody → me
Assignee: me → nobody
Priority: P2 → P3
Priority: P3 → P2
Assignee: nobody → me
Status: NEW → ASSIGNED
Whiteboard: [profiles] → [profiles][next]
Type: task → enhancement
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in before you can comment on or make changes to this bug.