[Trac] Master / Sub-Tickets

Hello all,

Trac accomplished the step to Python-3, which is good.
I am a long term Trac user and Open-Source developer;
Trac just works and provides everything I need.

Now I'm considering how best to proceed regarding *Mastertickets*,
which was an essential feature I'm heavily relying on: I have a
huge amount of tickets with a complex DAG of relationships,
which are essential for me to manage the work.

Mastertickets has a rather bare-bones UI, which relied on
post-processing of trac's template output.
So it seems this plug-in is broken beyond repair.


What are other people using for similar requirements?


There seem to be the

  - SubTickets plugin

  - ChildTickets plugin


As far as I can see, both support a DAG structure,
i.e. one ticket can be attached below several parents.

So it looks like it might be possible to cook up a SQL migration script.


Does anyone have experience with those plugins? are they still in use?
Both seem to have recent changes in the history. Are they ported to
python-3 and do they work with the new template engine, going forward?

Ideally I'd want to avoid putting much work into a migration
just to find out some time ahead that no one else is using
the plug-in and that it's unmaintained.

I do not have special requirements for the ticket workflow or for
reporting, yet I'd appreciate if a new solution performs a
dependency cycle check; mastertickets did that, and that was
quite helpful at times.

-- Hermann


-- 
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
To view this discussion visit https://groups.google.com/d/msgid/trac-users/43f369b7-18ab-4513-883a-da4a856de696%40ichthyostega.de.