On Mon, 2012-03-19 at 15:42 +0100, Brettschneider Falk wrote: > Roger Oberholtzer wrote: > > Currently, I will need to enter all the dates in each > > ticket. If a ticket slips it's date, I need to edit all the dependent > > tickets' dates by hand. This can be many tickets. And as the dates are > > going to change by an offset, batch modification is not possible. > When filling in the start and end date you must take care what > scheduling/showing the plan is and what just tracking of the results is > later. IMHO, the clear separation of plan and reality data is a missing > feature of that plugin. Though there's no problem, if you just use it > for making a plan that is adapted to changed needs from time to time. > Then it's up to you where dates must be changed and in which tickets, > how can the plugin do that for you?
Rules like: If ticket A can never start before ticket B starts, if ticket B gets it's start date moved, ticket A will too. Same with end of ticket. I have seen that the Grid Modify plugin lets you modify a set of tickets in a grid. I think you can fill in the fields of all tickets and then submit them. This way the fields for each ticket do not all get the same value, which is what the Batch Modify plugin does. Maybe my solution is to see how to do a query that gets the tickets as I want to edit the dates. Anyone using the Grid Modify plugin? > > CU, F@lk > > --- > Falk Brettschneider > R&D Software > Baumer Optronic GmbH > www.baumer.com > Geschaftsfuhrer: Marcel Seeber . Dr. Oliver Vietze > Sitz der Gesellschaft: Radeberg > Amtsgericht Dresden: HRB 15379 > Ust. ID: DE 189714583 > -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en.
