MasterTicket and SubTicket plugins

[Sam Halliday]

Sorry, this is a bit off-topic as it is about plugins.

I have seen that both MasterTicket and SubTicket plugins are trying to accomplish the same thing.

MasterTicket provides a graphviz view of ticket dependencies and I can't seem to get SubTickets to work with the latest TRAC dev.

But what functions do these plugins really provide? What are they doing that I can't already achieve with the following in my [custom-tickets] ?

blockedby = text

blockedby.label = Dependencies

blockedby.order = 5

blocking = text

blocking.label = Parents

blocking.order = 6

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 18.08.2012 16:23, schrieb Sam Halliday:
> Sorry, this is a bit off-topic as it is about plugins.

No, this is all right, it's about Trac plugin here as well. And while
t-h.o is down you have no choice anyway.

> I have seen that both MasterTicket and SubTicket plugins are trying to
> accomplish the same thing.

Not quite. Both of these address ticket hierarchy quite differently.

SubticketsPlugin is close to your work_package idea:
* allows for easy creation of child tickets, that have that ticket set
as parent
* provides mechanisms to ensure, that parent tickets are closed after
all childs have been closed, and no child can be changed after closing
the parent

MasterTicketsPlugin aims at implementing more diverse ticket
dependencies. Blockers, related tickets and so on. Really hope this gets
integrated into core, see some pointers below.

Steffen Hoffmann


[1] http://trac.edgewall.org/wiki/SubTickets
[2] http://trac.edgewall.org/wiki/TracCrossReferences
[3] http://bitbucket.org/moreati/trac-ticketlinks/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAvrewACgkQ31DJeiZFuHcUygCeMWF+S0yMtuPsrvI7z3WGnlUI
bf0An3Vq+jgNIGXpLuW5wk8zV6T1p34j
=wLqB
-----END PGP SIGNATURE-----

[Samuel Halliday]

OK, so Subtickets sound better because it would be good to be able to easily create a new subticket (which would have milestones and parent fields already filled out). The MasterTicket approach relies on manual entry of the ticket number, and as far as I can tell, doesn't even turn field values into clickable links.

The visualisation tools would be very useful when it is implemented.


I don't think this helps with the "work package" stuff we've been discussing ;-) That is still a different beast altogether.


--
Sam

> --
> You received this message because you are subscribed to the Google Groups "Trac Users" group.
> To post to this group, send email to trac-...@googlegroups.com.
> To unsubscribe from this group, send email to trac-users+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
>

[RjOllos]

On Saturday, August 18, 2012 7:23:19 AM UTC-7, Sam Halliday wrote:

I have seen that both MasterTicket and SubTicket plugins are trying to accomplish the same thing.

There is also ChildTicketsPlugin and ChildTicketTreeMacro. I spent very little amount of time looking at the Plugin, but it appeared similar to SubTicketsPlugin. 

[Samuel Halliday]

The ChildTicketsPlugin and ChildTicketTreeMacro plugins look nice because it provides visuals and a helpful input method. That said, it has some peculiar default settings (e.g. restricting the type of a child ticket, and using a non-standard "bug-fix" type).

Unfortunately I couldn't get the ChildTicketsPlugin to work properly for TRAC 1.0dev. The "create child" button that it is supposed to create doesn't seem to show up in tickets. Is the author around?

--
Sam

> --
> You received this message because you are subscribed to the Google Groups "Trac Users" group.

> To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/xDzNvtu4j-0J.

[Samuel Halliday]

I stand corrected on both accounts! The defaults are sensible (everything is turned off by default) and it does work in dev.

RjOllos - thanks for the heads up, this is the best dependency management solution for TRAC I've seen yet.

--
Sam

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 21.08.2012 21:14, schrieb Samuel Halliday:
> I stand corrected on both accounts! The defaults are sensible
> (everything is turned off by default) and it does work in dev.

Nice. I tried it too, and while its totally-off-by-default is sensible,
it has been initially disturbing to me as well. Maybe the wiki
documentation accounts for that.?

> RjOllos - thanks for the heads up, this is the best dependency
> management solution for TRAC I've seen yet.

Maybe, but I'd love to see more energy going into a solution in Trac
core. There's a veeery old ticket [1] with work done on it, but
unluckily nothing closed to meeting Trac standards yet, or should I say
Trac core developer attention?

So sad to guess, that we'll certainly see Trac 1.0 without that powerful
ticket dependencies, and the 9th anniversary of the aforementioned
ticket on 2012-01-29 most likely too. These circumstances take a lot of
the initial happiness about any ticket dependency plugin away from me.

Steffen Hoffmann


[1] #31 - Bug dependencies/relations feature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlA2idMACgkQ31DJeiZFuHfWnQCeLI9Jowh+ne7laGo9r1+CD5Fk
ig8An1Avox9aIlFacrIYKheuIVSv0Mns
=EfLa
-----END PGP SIGNATURE-----

[Grzegorz Sobański]

On 18.08.2012 16:23, Sam Halliday wrote:
> I have seen that both MasterTicket and SubTicket plugins are trying
> to accomplish the same thing.

As I see it both of those plugins supply different things. And it is
normal to have both installed.

Subticket is representing ticket hierarchy, for example you have a big
task that is divided into smaller tasks (=child tickets). All of those
tickets are somehow related.

Mastertickets and fields blocking/blockedby are exactly for that -
indicating that some ticket is locked by some other, and those tickets
can be totally unrelated. For example:
ticket #123: Extending internal trac to support ordering coffe
is blocked by
ticket #234: Deliver second monitor to developers
Rationale: i can't develop without two monitors on desk
But those tickets don't share a hierarchy, are not part of the same
bigger task, etc, etc.

> But what functions do these plugins really provide? What are they doing
> that I can't already achieve with the following in my [custom-tickets] ?
>
> blockedby = text
> blockedby.label = Dependencies
> blockedby.order = 5
> blocking = text
> blocking.label = Parents
> blocking.order = 6

Mastertickets automatically fills the corresponding field in the second
ticket - if you set blockedby #2 on #1, then blocking is set to #1 on #2.

Generally both of those plugins supplie some automation in filling those
custom fields. Without them it would be tedious to keep everything in
sync.

Hope this helps.

--
silk

[Grzegorz Sobański]

On 18.08.2012 17:09, Samuel Halliday wrote:
> The MasterTicket approach relies on manual entry of the ticket number,
> and as far as I can tell, doesn't even turn field values into
clickable links.

It does make clickable links in blockedby and blocking fields.


--
silk