-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alex Willmer wrote: > On Mon, Nov 8, 2010 at 1:14 PM, Chris Nelson <[email protected]> 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/
Good to know. Cloning and working on it is easy then. > [...] > 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 I've not looked into this closely. Just from a remote point of view I see issues with preparing i18n support for this. Without a fixed set of default labels we have nothing for translators, and no localized string to display in internationalized Trac environments, that use multiple languages concurrently. Apart from this it looks as flexible as the configurable ticket work-flow, great. And please have configurable columns with a really minimal set to start from. Just relation type, ID, summary and status will do. > [...] > I have looked at SubTicketsPlugin, but I had not seen that patch thank > you. I shall take a look and possibly do similar. IMO one great think to learn from SubTicketsPlugin is the convenience created by the (New) link for creating new children. I'm about to increase this even more by adding some code for duplicating some ticket settings like milestone, keywords, etc. from parent to that new child. Something that could be worth implementing for every relation. >>> - '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. +1 from me, as mentioned above. BTW, as I non-native speaker I'm unsure, if 'linked' is a good word for every part of a final implementation. I'd like to see 'related' instead of 'linked', as it sounds less technical. We may have some weaker relations than parent-child and blockers, like suggested in http://trac.edgewall.org/ticket/31. I.e. just a 'related' to pass notifications forth and back between the marked tickets. >> [...] >> 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. Looks like to me too. I remember having read a comment somewhere in the pile of discussion contributions, that the whole relation stuff could be totally pointless for users, only for developers working at the issues reported. I'm not decided on a (better) different presentation, but increasing the ticket header by 50 % just for two relation dimensions rings a field bloat alarm bell. IMO bringing in the 'create new ticket with same relation' buttons and some more relations to choose from, will require a better visual representation. Steffen Hoffmann (hasienda) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkzZqhAACgkQ31DJeiZFuHd0CACfZtH81gi3d+O1VCshU1Pr69ym 9EUAnRJwajWsYXA47iT7F+sYD0MF7M8/ =pkAQ -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
