Closed (fixed)
Project:
Project issue tracking
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
6 Jul 2011 at 19:12 UTC
Updated:
26 Mar 2012 at 05:20 UTC
Introduced in the initial #425728: Add an "issue cockpit" block for project nodes patch,
from all possible project metrics, the "Oldest open issue" is the most bogus one and does not have any meaning.
Prime example: Until 2009, the cockpit would have shown "2001" due to #8: Let users cancel their accounts... and what does that tell us? Nada.
| Comment | File | Size | Author |
|---|---|---|---|
| project_issue.cockpit-oldest.0.patch | 1.17 KB | sun |
Comments
Comment #1
webchickI'm not sure; I think it's helpful. It gives good incentive to clean up bogus issues with no meaning and close them.
Also, IIRC the fact that this was Drupal's oldest open issue is how you ended up on node/8 anyway. :)
Comment #2
sunI have countless stone-age issues in my project's queues, which I'd love to resolve at some day, but (most often external) factors block them. This means nothing.
Actually not. I ran into the problem of users wanting to cancel their accounts, so I merely searched the queue for matching issues. Didn't even realize it was that of an odd issue number at the beginning.
Comment #3
sunAlso, forgot to mention in the OP and in #2:
This is FOSS.
Comment #4
moshe weitzman commentedI agree that it is meaningless. And it isn't even hyperlinked so you could read and act on it.
@webchick - shame is not a good motivator.
Comment #5
dwwThis was originally proposed from Leisa and Mark during mockups for the d.o redesign. See #425728: Add an "issue cockpit" block for project nodes for background. That said, generally the redesign didn't get very far with Project*-related UX. They just didn't have the time to do their thorough process on Project* that they did on more of the outward-facing parts of the site, so generally, we're more free to do whatever we think is best since their mockups were just sketches/suggestions, not a detailed design. Therefore, I lean towards killing this line, but I just wanted to explain the history a bit.
If people want to clean up old issues, it'd be better to expose some tools in advanced search so you can sort by issue creation time (currently, you can only sort by last update). Then you could actually act on things. But that's for a separate issue (which AFAIK doesn't yet exist).
Comment #6
webchickEh? Issue queues have a "created" column since a few months now. :) You committed and deployed the patch. :D #1179586: Add 'created' date column to issue queue views
Comment #7
webchickOh, and given that we have the ability to find crufty stuff that way now, I agree that this is a meaningless metric and can be removed.
Comment #8
dwwTee hee. ;) It's been a hard few months and my aging brain is clearly turning into mud. Thanks for reminding me. ;)
Committed and pushed. This will go live when I deploy #1304550: Display count of issue followers when viewing an issue (which is blocked on #1477994: Create jenkins job for clearing the varnish cache when deploying CSS/JS changes or finding nnewton in IRC *sigh*).