Percentages should be color coded.

Bug #256969 reported by Jorge Castro
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Undecided
Graham Binns

Bug Description

On the upstream report: https://edge.launchpad.net/ubuntu/+upstreamreport

Statistical columns with a value of < 20% should be coloured red. Columns should be coloured green according to their existing 'good' thresholds. All other columns should remain white.

Jorge Castro (jorge)
Changed in launchpad:
assignee: nobody → gmb
Graham Binns (gmb)
Changed in launchpad:
milestone: none → 2.1.8
Graham Binns (gmb)
Changed in launchpad:
status: New → In Progress
Graham Binns (gmb)
Changed in launchpad:
milestone: 2.1.8 → none
Changed in malone:
milestone: none → 2.1.8
Changed in malone:
milestone: 2.1.8 → 2.1.9
Graham Binns (gmb)
description: updated
Revision history for this message
Martin Albisetti (beuno) wrote :

After talking to Jorge, here a few tips:

- Remove the bugtracker column
- Remove the upstream contact column
- Make the full row red or green (maybe lighter shades?)

That's all I can think of for now, but I'll be happy to look at it again when these changes have been applied :)

Revision history for this message
Christian Reis (kiko) wrote : Re: [Bug 256969] Re: Percentages should be color coded.

On Tue, Sep 09, 2008 at 07:17:04PM -0000, Martin Albisetti wrote:
> - Remove the bugtracker column
> - Remove the upstream contact column

By removing these, we lose the only view which allows us to verify how
good our coverage in these aspects is of the most important packages. Is
the issue real estate? Might be smarter to find a way to condense that
information.

Revision history for this message
Martin Albisetti (beuno) wrote :

I forgot to also mention: "remove the project column, and make it a tooltip for the package"

Revision history for this message
Martin Albisetti (beuno) wrote :

On Tue, Sep 9, 2008 at 6:19 PM, Christian Reis <email address hidden> wrote:
> On Tue, Sep 09, 2008 at 07:17:04PM -0000, Martin Albisetti wrote:
>> - Remove the bugtracker column
>> - Remove the upstream contact column
>
> By removing these, we lose the only view which allows us to verify how
> good our coverage in these aspects is of the most important packages. Is
> the issue real estate? Might be smarter to find a way to condense that
> information.

This is actually the result of a conversation with Jorge, who thought
those could be removed (ie, they weren't important).
If they are, we can maybe use a tick or cross to show if the upstream
contact is available?

I agree we can condense it better, I just need to know what the
purpose of this page is :)

--
Martin

Revision history for this message
Jorge Castro (jorge) wrote :

I like the idea of a tick or cross to show if it's available. Like kiko hinted, my main issues is it was dominating the page with it's huge width and tons of red.

I think the bugtracker info can go, these are the top100 projects by open bugs, by the time they make this list the bug trackers are filled in. (Ignoring the projects in which we are upstream of course.)

Revision history for this message
Graham Binns (gmb) wrote :

Marking this won't fix since it needs to be split up into several bugs based on Martin's recommendations above.

Changed in malone:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.