One option may be the Queues plugin: http://trac-hacks.org/wiki/QueuesPlugin
The Queues plugin was designed to explicitly order a backlog by priority similar to what you describe below. It's main mechanism is drag-and-drop but you can couple it with GridModify to enable a Netflix-like priority queue behavior. (We made a slight mod to GridModify to require a button click to enable it so that it's not enabled by default - that's a simple jQuery addition.) Happy to answer specific questions about this plugin if you have any. Cheers. - Rob On Feb 21, 2012, at 10:12 AM, Jean-Francois Bouchard wrote: > Hello, > > Let me explain the basic. > > That list of 300 tickets is a feature backlog. With an unique index, a > group in our organization will be able to dictate exactly what feature > goes next to the RandD group. > > Do you see what way of doing this ? While maintaining the manageability ? > > Thanks, > > JF > > On Mon, Feb 20, 2012 at 6:49 PM, Benjamin Lau <benjamin.a....@gmail.com> > wrote: >>> Feature : A way to add a numerical field that can be managed in bulk. >>> This field will be our priority for about 300 tickets. (It will >>> basically order the list). >> >> So Steffen tried to help you with a technical solution to the >> problem... but I think you might have a different problem entirely. >> >> Why exactly do you need to have a priority for all 300+ tickets? As >> Steffen mentioned in his thoughts about a technical solution related >> to the large number of ticket change updates, the fact that there >> would be this huge number of updates (lets say I insert a ticket at >> slot 150... I now have to update all of the tickets after it...). The >> fact that horrible and ugly things like this are happening makes me >> suspect there's probably an issue with the process that your using. >> >> If you need finer grained management of the tickets... why not make >> use of Trac's existing grouping capabilities? You can group tickets in >> a variety of ways using Milestones, Components, Priorities, Severities >> to achieve an extremely fine grain classification of your tickets. And >> if this is for a software development project... are you really >> working through 300+ tickets in such a short period of time and with >> enough developers that keeping order across the ticket pool is even >> necessary? >> >> Investing the time to develop a custom Trac plug-in is a >> liability[1,2]... maybe a change to your processes could be made that >> would save you the trouble since what you're currently proposing >> sounds overly complex to me. >> >> Ben >> [1] http://teddziuba.com/2010/10/taco-bell-programming.html >> [2] >> http://teddziuba.com/2010/12/the-3-basic-tools-of-systems-engineering.html >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Trac Development" group. >> To post to this group, send email to trac-dev@googlegroups.com. >> To unsubscribe from this group, send email to >> trac-dev+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/trac-dev?hl=en. >> > > -- > > > Avis de confidentialité > > Les informations contenues dans le présent message et dans toute pièce qui > lui est jointe sont confidentielles et peuvent être protégées par le secret > professionnel. Ces informations sont à l’usage exclusif de son ou de ses > destinataires. Si vous recevez ce message par erreur, veuillez s’il vous > plait communiquer immédiatement avec l’expéditeur et en détruire tout > exemplaire. De plus, il vous est strictement interdit de le divulguer, de > le distribuer ou de le reproduire sans l’autorisation de l’expéditeur. > Merci. > > Confidentiality notice > > This e-mail message and any attachment hereto contain confidential > information which may be privileged and which is intended for the exclusive > use of its addressee(s). If you receive this message in error, please > inform sender immediately and destroy any copy thereof. Furthermore, any > disclosure, distribution or copying of this message and/or any attachment > hereto without the consent of the sender is strictly prohibited. Thank you. > > -- > You received this message because you are subscribed to the Google Groups > "Trac Development" group. > To post to this group, send email to trac-dev@googlegroups.com. > To unsubscribe from this group, send email to > trac-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/trac-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
