On Jun 23, 2008, at 1:13 PM, Alec Thomas wrote:
> > 2008/6/24 Scott Bussinger <[EMAIL PROTECTED]>: >> >>> Christian has made a very useful report on the popular tickets: >>> http://trac.edgewall.org/report/32 >> >> This _is_ an interesting report. To make it truly useful though I >> think would require two things: >> >> 1) Explicitly stating that development on the project is going to be >> at least partially guided by the number of people who "vote" for a >> feature request by entering themselves in the CC field. >> >> 2) A definite show of support from the active developers on the >> project to actually implement some of the popular features requested >> (either in the core or as a supported plugin). > > I agree 100%. I think we need to shift to a model of actively trying > to > implement features users want. Workflow is a good example of this, but > we need to continue. Can we install VotePlugin on t.e.o? I have a report to do summaries using that instead and it might be clearer to people that those numbers matter. SELECT p.value AS __color__, id AS ticket, sum(v.vote) as votes, summary, component, version, milestone, t.type AS type, owner, status, time AS created, changetime AS _changetime, description AS _description, reporter AS _reporter FROM ticket t, enum p, votes v WHERE status <> 'closed' AND p.name = t.priority AND p.type = 'priority' AND v.resource = 'ticket/' || id GROUP BY id, summary, component, version, milestone, t.type, owner, time, changetime, description, reporter, p.value, status ORDER BY votes DESC, milestone, t.type, time --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
