Data consistency on batch updated of parent-id

[anonymous]

Hi,

I'm new to Trac and this plugin enables a lot of workflows that I need (backlog reviews, epics). One thing that would really speed up / simplify some of our processes is the ability to select a number of tickets and assign them in bulk to a new parent.

I've tested this and the parent-id is set on the child tickets correctly (although, circumvents permissions but I'm happy to live with that) but it is obviously not updating a table somewhere else because the parent task doesn't see the child tasks.

I'm happy to look at this and provide a patch if I get a chance, but would be happy to take some pointers from someone more familiar with the code base.

Cheers,

Gary

[Ryan J Ollos]

Replying to anonymous:

One thing that would really speed up / simplify some of our processes is the ability to select a number of tickets and assign them in bulk to a new parent.

I'll assume you are referring to TicketBatchModify.

I've tested this and the parent-id is set on the child tickets correctly (although, circumvents permissions but I'm happy to live with that)

The ticket manipulators aren't called prior to implementation of ​trac:#11723 (Implemented in Trac 1.3.2, will be released with Trac 1.4).

but it is obviously not updating a table somewhere else because the parent task doesn't see the child tasks.

The plugin doesn't have any tables. The parent ticket ids are stored in Trac's ticket-custom table and the cache is updated when a ticket is changed: childticketsplugin/trunk/childtickets/childtickets.py@17042:22-30,33-35#L16​.

Make sure you prefix the ticket ids with # when updating using batch modify.

[anonymous]

Thanks for the insights. I've tested on 1.3.2 and works as expected. Thanks.