[Trac] Re: Master / Sub-Tickets

------=_Part_610064_1680533944.1765817852507
Content-Type: multipart/alternative; 
	boundary="----=_Part_610065_382573323.1765817852507"

------=_Part_610065_382573323.1765817852507
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Did my own port from early 2023 to Trac 1.5.4 / Py3 including some personal=
=20
modifications ... that probably won't help ...
You might want to try the patch for Trac 1.6 / Py3=20
from: https://trac-hacks.org/ticket/14336#no2
-- Stefan

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

> I'm not sure if I can help out a lot with this, but FYI my group is using=
=20
> child tickets plugin.  It does check for open child tickets and prevent=
=20
> closing the parent if so.
>
> Yes, we've been using Python 3 version for for quite a few years.  I=20
> ported a few plugins myself, but it's been a while lol ... the data is no=
t=20
> in cache right now ...
>
> - Dan
>
> On Monday, December 15, 2025 at 9:53:50=E2=80=AFAM UTC-6 ichthyo wrote:
>
>>
>> Hello all,=20
>>
>> Trac accomplished the step to Python-3, which is good.=20
>> I am a long term Trac user and Open-Source developer;=20
>> Trac just works and provides everything I need.=20
>>
>> Now I'm considering how best to proceed regarding *Mastertickets*,=20
>> which was an essential feature I'm heavily relying on: I have a=20
>> huge amount of tickets with a complex DAG of relationships,=20
>> which are essential for me to manage the work.=20
>>
>> Mastertickets has a rather bare-bones UI, which relied on=20
>> post-processing of trac's template output.=20
>> So it seems this plug-in is broken beyond repair.=20
>>
>>
>> What are other people using for similar requirements?=20
>>
>>
>> There seem to be the=20
>>
>> - SubTickets plugin=20
>>
>> - ChildTickets plugin=20
>>
>>
>> As far as I can see, both support a DAG structure,=20
>> i.e. one ticket can be attached below several parents.=20
>>
>> So it looks like it might be possible to cook up a SQL migration script.=
=20
>>
>>
>> Does anyone have experience with those plugins? are they still in use?=
=20
>> Both seem to have recent changes in the history. Are they ported to=20
>> python-3 and do they work with the new template engine, going forward?=
=20
>>
>> Ideally I'd want to avoid putting much work into a migration=20
>> just to find out some time ahead that no one else is using=20
>> the plug-in and that it's unmaintained.=20
>>
>> I do not have special requirements for the ticket workflow or for=20
>> reporting, yet I'd appreciate if a new solution performs a=20
>> dependency cycle check; mastertickets did that, and that was=20
>> quite helpful at times.=20
>>
>> -- Hermann=20
>>
>>
>>

--=20
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 e=
mail to trac-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
To view this discussion visit https://groups.google.com/d/msgid/trac-users/=
f05ac984-cf6a-4f2a-b281-144f37604812n%40googlegroups.com.

------=_Part_610065_382573323.1765817852507
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div>Did my own port from early 2023 to Trac 1.5.4 / Py3 including some per=
sonal modifications ... that probably won't help ...</div><div></div><div><=
/div><div>You might want to try the patch for Trac 1.6 / Py3 from:=C2=A0htt=
ps://trac-hacks.org/ticket/14336#no2</div><div>-- Stefan</div><br /><div cl=
ass=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_attr">Dan schrieb am M=
ontag, 15. Dezember 2025 um 17:38:30 UTC+1:<br/></div><blockquote class=3D"=
gmail_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, =
204, 204); padding-left: 1ex;"><div>I&#39;m not sure if I can help out a lo=
t with this, but FYI my group is using child tickets plugin.=C2=A0 It does =
check for open child tickets and prevent closing the parent if so.</div><di=
v><br></div><div>Yes, we&#39;ve been using Python 3 version for for quite a=
 few years.=C2=A0 I ported a few plugins myself, but it&#39;s been a while =
lol ... the data is not in cache right now ...</div><div><br></div><div>- D=
an</div><br><div class=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_att=
r">On Monday, December 15, 2025 at 9:53:50=E2=80=AFAM UTC-6 ichthyo wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>Hello all,
<br>
<br>Trac accomplished the step to Python-3, which is good.
<br>I am a long term Trac user and Open-Source developer;
<br>Trac just works and provides everything I need.
<br>
<br>Now I&#39;m considering how best to proceed regarding *Mastertickets*,
<br>which was an essential feature I&#39;m heavily relying on: I have a
<br>huge amount of tickets with a complex DAG of relationships,
<br>which are essential for me to manage the work.
<br>
<br>Mastertickets has a rather bare-bones UI, which relied on
<br>post-processing of trac&#39;s template output.
<br>So it seems this plug-in is broken beyond repair.
<br>
<br>
<br>What are other people using for similar requirements?
<br>
<br>
<br>There seem to be the
<br>
<br>  - SubTickets plugin
<br>
<br>  - ChildTickets plugin
<br>
<br>
<br>As far as I can see, both support a DAG structure,
<br>i.e. one ticket can be attached below several parents.
<br>
<br>So it looks like it might be possible to cook up a SQL migration script=
.
<br>
<br>
<br>Does anyone have experience with those plugins? are they still in use?
<br>Both seem to have recent changes in the history. Are they ported to
<br>python-3 and do they work with the new template engine, going forward?
<br>
<br>Ideally I&#39;d want to avoid putting much work into a migration
<br>just to find out some time ahead that no one else is using
<br>the plug-in and that it&#39;s unmaintained.
<br>
<br>I do not have special requirements for the ticket workflow or for
<br>reporting, yet I&#39;d appreciate if a new solution performs a
<br>dependency cycle check; mastertickets did that, and that was
<br>quite helpful at times.
<br>
<br>-- Hermann
<br>
<br>
<br></blockquote></div></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Trac Users&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:trac-users+unsubscribe-/[email protected]">trac-use=
rs+unsubscribe-/[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
trac-users/f05ac984-cf6a-4f2a-b281-144f37604812n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/trac-use=
rs/f05ac984-cf6a-4f2a-b281-144f37604812n%40googlegroups.com</a>.<br />

------=_Part_610065_382573323.1765817852507--

------=_Part_610064_1680533944.1765817852507--