Alex Willmer wrote: > On Mon, Nov 8, 2010 at 1:14 PM, Chris Nelson > <chris.nel...@sixnet.com> wrote: >> Alex Willmer wrote: >>> I am doing some enhancements to the ticket-links branch (http:// >>> trac.edgewall.org/browser/ticket-links) on behalf of Logica. Namely >>> to add the features: > > I've now uploaded my work in process here > https://bitbucket.org/moreati/trac-ticketlinks/
It's exciting to see this being worked on. If I can contribute, let me know. > It is based on cboos ticket-links branch > http://svn.edgewall.org/hg/trac/topic/ticket-links > > A screen shot of the current code http://twitpic.com/35ddf6 > The trac.ini [ticket-links] currently looks like > [ticket-links] > dependency = dependson,dependant > dependency.validator = no_cycle > dependson.label = Depends on > dependson.blocks = true > dependant.label = Dependant > parentchild = parent,children > parentchild.validator = parent_child > parent.label = Parent > children.label = Child > children.blocks = true How is no_cycle different from parent_child? I imagine parent_child has more than no_cycle. It's only just occurred to me that cycles have to be detected along all possible links. For example, A has a child B which blocks C which blocks A. >>> - 'Blocking/blocked by' link type >> >> Like MasterTickets plugin >> (http://trac-hacks.org/wiki/MasterTicketsPlugin)? > > Yes 'blocking/blocked by' linked should behave similarly to > MasterTickets relationships. > >>> - Display of linked issues on the ticket page as shown in the >>> RedMine screenshot http://trac.edgewall.org/ticket/31#comment:147 >> >> Have you looked at Subtickets plugin >> (https://github.com/itota/trac-subtickets-plugin)? It has a list of >> child tickets. (At >> https://github.com/itota/trac-subtickets-plugin/issues/#issue/9, I >> added >> a patch to allow configurable columns.) > > I have looked at SubTicketsPlugin, but I had not seen that patch thank > you. I shall take a look and possibly do similar. Another thing I like about the Subtickets child list is that the text is slightly smaller than normal ticket list display so it doesn't take up quite as much room. I think I'd like to keep blocking/blocked by in the custom field display and children at the bottom. Perhaps this is a "Yogi Berra problem" ("When you get to a fork in the road, take it!"). That is, what's in the list should be configurable: no list, children, predecessors/successors, all. >>> - 'Create linked ticket' user interface >> >> Not sure what you mean here. > > By this I mean a button or drop down placed on the page for a ticket > (e.g. #1). When the user clicks it they're taken to the create new > ticket page and certain fields a pre-populated. When saved the new > ticket is linked to the original, as e..g a child, or dependant. OK. I'll have to get my plugin on T-H. In the mean time, my configuration is: [ticket-create-buttons] blockedby.tag = .//t...@headers="h_blockedby"] blockedby.label = Create blockedby.title = Create a new predecessor blockedby.inherit = type, milestone blockedby.link = blocking:id The new ticket will have the same type and milestone as the current ticket and its blocking will be this tickets's ID. >>> ... > ... >> I've created a plugin that puts buttons next to fields in the ticket >> header to create a new sibling ticket (next to Subtickets' parents >> field), create a new predecessor (next to MasterTickets' blockedby >> field) and create a new successor (next to MasterTickets' blocking >> field). Subtickets provides a link to create new children. > > These plugins sound similar to the 'Create linked ticket' I spoke of. Yes, they serve the same function. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
