http://localhost/ticket/2432 <p> We want a new way of working with trac tickets and milestones etc: </p> <ul><li>We will have a single queue of tickets, ordered by priority, that we all work on </li></ul><ul><li>Tickets only get into the queue after triaging (which the devs do at regular intervals), so we and others can use new trac tickets as a dumping ground for any and all CKAN bugs and ideas without messing up the priority queue. Therefore the priority queue needs to be a special CKAN milestone or something. The devs need to regularly go through the inbox of untriaged tickets and triage them all, moving them all out of the inbox. </li></ul><ul><li>Will we also assign tickets from the priority queue to individual devs in sprint planning meetings like we currently do? </li></ul> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/2432 Trac 0.12.3 aron.carroll Mon, 28 May 2012 11:45:26 GMT http://localhost/ticket/2432#comment:1 http://localhost/ticket/2432#comment:1 <p> It would be great to use something like <a class="ext-link" href="http://trac-hacks.org/wiki/SimpleTicketPlugin"><span class="icon">​</span>http://trac-hacks.org/wiki/SimpleTicketPlugin</a> to remove most of the options when creating a ticket. </p> <p> Suggestions to remove theme, repository, component and type unless they're actually useful. </p> Ticket seanh Mon, 28 May 2012 11:54:27 GMT http://localhost/ticket/2432#comment:2 http://localhost/ticket/2432#comment:2 <ul> <li><strong>priority</strong> changed from <em>awaiting triage</em> to <em>major</em> </li> <li><strong>milestone</strong> changed from <em>current-ckan-sprint-2012-05-29</em> to <em>current-ckan-sprint-2012-06-25</em> </li> </ul> Ticket seanh Tue, 29 May 2012 18:26:10 GMT http://localhost/ticket/2432#comment:3 http://localhost/ticket/2432#comment:3 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> Ticket shevski Tue, 29 May 2012 20:58:40 GMT http://localhost/ticket/2432#comment:4 http://localhost/ticket/2432#comment:4 <p> Where do new tickets go to await triaging? Is priority set by whoever creates the ticket? Does this get revised? Will we have a field for dev time estimate or where will this go? </p> Ticket