Master / Sub-Tickets

[ichthyo]

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

[Dan]

I'm not sure if I can help out a lot with this, but FYI my group is using child tickets plugin.  It does check for open child tickets and prevent closing the parent if so.

Yes, we've been using Python 3 version for for quite a few years.  I ported a few plugins myself, but it's been a while lol ... the data is not in cache right now ...

- Dan

[ichthyo]

On 15/12/2025 17:38, Dan wrote:
> I'm not sure if I can help out a lot with this, but FYI my group is using child
> tickets plugin.  It does check for open child tickets and prevent closing the
> parent if so.

Thanks, good to know. At least someone is using it...

> Yes, we've been using Python 3 version for for quite a few years.

Which version of Trac are you on?

>  I ported a few plugins myself, but it's been a while lol ...

Indeed, the porting to python-3 is usually not that hard,
in most cases it boils down to turning "print" into a function
and then to figure out where generators are used, because these
do not return a list any more.

But with Trac there is also the twist with the move away from
the Genshi templating engine, which allowed for post-processing.
If a plugin relied on that in a substantial way(as mastertickets did),
then just porting is not enough, it would require a complete rewrite.

Thanks anyway for your answer, very much appreciated

-- Hermann

[Dan]

On 1.6 now.  I think we used a pre-release 1.5 version for a while with Python 3 as well.  I tried getting my plugins ported before 1.6 came out.

Yes, the loss of Genshi is the real problem, it seems to me.  I did a couple conversions for that.

- Dan

[stefgers]

I'm also heavily using the MasterTicketsPlugin ...

I'm using my own port from early 2023 to Trac 1.5.4 including some personal modifications. This probably won't help in your case ...

But I found a patch for Trac 1.6 with Python 3 available at: https://trac-hacks.org/ticket/14336

You should give this a try! ;-)

-- Stefan

[stefgers]

Did my own port from early 2023 to Trac 1.5.4 / Py3 including some personal modifications ... that probably won't help ...

You might want to try the patch for Trac 1.6 / Py3 from: https://trac-hacks.org/ticket/14336#no2

-- Stefan

Dan schrieb am Montag, 15. Dezember 2025 um 17:38:30 UTC+1: