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: > > - 'Blocking/blocked by' link type
Like MasterTickets plugin (http://trac-hacks.org/wiki/MasterTicketsPlugin)? > - 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.) > - 'Create linked ticket' user interface Not sure what you mean here. > ... > 2. The Ticket object currently only exposes that ticket's links in a > string (e.g. Ticket(env, 1).values['dependants'] == '#2, #3'), which > is not ideal when rendering the linked tickets in a different form > (e.g an ordered list or table). Rather than split this string > repeatedly with ticket_system.parse_links() I would like to hold the > links read from the database as an attribute of the ticket > e.g. Ticket(env, 1).ends['dependants'] == [2, 3] or Ticket(env, > 1).links['dependants'] == [2, 3]). > Is this a bad idea? I admit to being on the fence about this. Our ticket dependency work is currently based on MasterTickets (for predecessors and successors) and Subtickets (for children/sub-tasks). MasterTickets keeps an external relation *and* keeps custom fields (blocking, blockedby) in sync with every ticket change. Subtickets keeps a external relation and keeps only a parents[sic] custom field current in the ticket change listener but does all of its hard work in ticket validation using the relation. We have left both plugins' dependency displays in place: predecessors and successors are shown at the top of the ticket and children are listed at the bottom of the Description. What I'd really like is a "local Gannt" which showed the current ticket and it's immediate predecessor, successor, ancestor, and children. 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. -- 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.
