Changes between Version 25 and Version 26 of ChildTicketsPlugin
- Timestamp:
- Mar 19, 2015, 10:32:36 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ChildTicketsPlugin
v25 v26 1 1 [[PageOutline(2-5,Contents,pullout)]] 2 2 3 = Support for pseudo child-tickets and a visual reference to these within a parent ticket . =3 = Support for pseudo child-tickets and a visual reference to these within a parent ticket 4 4 5 == Description ==5 == Description 6 6 7 7 Some time ago I came across the problem of how to manage child tickets in a meaningful fashion, we were using [wiki:coderanger]'s original [wiki:MasterTicketsPlugin] and it was great until we started to allow tickets to be viewed and created by people outside of our immediate development group. We found that people who were not familiar with our processes would simply create child tickets of the wrong 'type' and needed some help in getting it right. In addition, users found that the lack of visual information (ie. what are this tickets child tickets?) was also a hindrance. 8 8 9 Having child-tickets is extremely useful when it comes to managing multiple releases (ie. a single 'bug-report' ticket and a single 'bug-fix' ticket for each milestone/branch of development), for managing sub-tasks of an issue and for managing 'bug-fixes' required when developing a new (larger) enhancement.9 Having child-tickets is useful when multiple releases need to be managed. For example for s single 'bug-report' ticket and a single 'bug-fix' ticket for each milestone/branch of development, for managing sub-tasks of an issue and for managing 'bug-fixes' required when developing a new (larger) enhancement. 10 10 11 This plugin modifies the ticket description box and adds a child ticket listing table and a 'create' button for adding new child tickets. It has the following features:11 This plugin modifies the ticket description box and adds a child ticket listing table and a 'create' button for adding new child tickets. 12 12 13 13 It is possible to control in trac.ini the following aspects of child-ticket creation/viewing: … … 19 19 Under Trac 0.10 I had to modify the ticket.html templates to get this working in any 'pretty' sense so I have not provided support for 0.10. As of 0.11, the ITemplateStreamFilter allows this to be incorporated nicely into a neat plugin. 20 20 21 In order to keep the plugin as compact and simple as possible and to allow future compatibility with different CSS schemes, I have simply 'pinched' the existing CSS classes for generating the table and its components.21 In order to keep the plugin compact and simple and to allow future compatibility with different CSS schemes, I have simply 'pinched' the existing CSS classes for generating the table and its components. 22 22 23 NOTE: The configurability of this plugin has been ported to the Subtickets plugin.See the patches in issues 9-12 at [http://github.com/itota/trac-subtickets-plugin/issues github]. -- Chris Nelson23 '''Note''': The configurability of this plugin has been ported to the Subtickets plugin. See the patches in issues 9-12 at [http://github.com/itota/trac-subtickets-plugin/issues github]. -- Chris Nelson 24 24 25 == Configuration ==25 == Bugs/Feature Requests 26 26 27 The plugin makes use of the 'ticket-custom' field and so requires no extra db tables to be created. The following fields are required in the 'trac.ini' (see table below for a generic description of the options): 27 Existing bugs and feature requests for ChildTicketsPlugin are 28 [report:9?COMPONENT=ChildTicketsPlugin here]. 29 30 If you have any issues, create a 31 [http://trac-hacks.org/newticket?component=ChildTicketsPlugin&owner=walnut new ticket]. 32 33 [[TicketQuery(component=ChildTicketsPlugin&group=type,format=progress)]] 34 35 == Download 36 37 Download the zipped source from [download:childticketsplugin here]. 38 39 == Source == 40 41 You can check out ChildTicketsPlugin from [http://trac-hacks.org/svn/childticketsplugin here] using Subversion, or [source:childticketsplugin browse the source] with Trac. 42 43 == Configuration 44 45 The plugin makes use of the 'ticket-custom' field and so requires no extra database tables to be created. The following fields are required in the `trac.ini` file: 28 46 29 47 {{{ … … 39 57 40 58 [childtickets] 41 42 59 # 'enhancements' : child tickets will typically be bug-fix tickets with the same milestone, component and keywords. 43 60 parent.enhancement.allow_child_tickets = true … … 62 79 # 'task' : child tickets are not allowed. 63 80 parent.task.allow_child_tickets = false 64 65 81 }}} 66 82 67 === [childtickets] === 83 See table below for a generic description of the options. 84 85 === [childtickets] 68 86 69 87 {{{ … … 79 97 }}} 80 98 81 == Issues / Caveats ==99 == Issues / Caveats 82 100 83 101 * If you change the behaviour of the parent type (using for example allow_child_tickets/restrict_child_type) and tickets already have child tickets assigned to them you will not receive a warning about any possible conflicts until you try and modify any of the child tickets. … … 85 103 * The 'parent.<type>.inherit' option ensures fields are inherited by child tickets, However, all child tickets (regardless of type as defined by 'restrict_child_type') will inherit these values. 86 104 87 == Bugs/Feature Requests == 88 89 Existing bugs and feature requests for ChildTicketsPlugin are 90 [report:9?COMPONENT=ChildTicketsPlugin here]. 91 92 If you have any issues, create a 93 [http://trac-hacks.org/newticket?component=ChildTicketsPlugin&owner=walnut new ticket]. 94 95 == Download == 96 97 Download the zipped source from [download:childticketsplugin here]. 98 99 == Source == 100 101 You can check out ChildTicketsPlugin from [http://trac-hacks.org/svn/childticketsplugin here] using Subversion, or [source:childticketsplugin browse the source] with Trac. 102 103 == Examples == 105 == Examples 104 106 105 107 Some examples [wiki:ChildTicketsPlugin/Examples here]. 106 108 109 == Recent Changes 107 110 108 == Recent Changes == 109 110 [[ChangeLog(childticketsplugin, 5)]] 111 [[ChangeLog(childticketsplugin, 3)]] 111 112 112 113 == Author/Contributors == 113 114 114 115 '''Author:''' [wiki:walnut] [[BR]] 115 '''Maintainer:''' [ wiki:walnut] [[BR]]116 '''Maintainer:''' [[Maintainer]] [[BR]] 116 117 '''Contributors:'''