Changes between Version 9 and Version 10 of ChildTicketsPlugin
- Timestamp:
- Feb 12, 2011, 11:11:27 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ChildTicketsPlugin
v9 v10 14 14 * allow/disallow child-tickets for a certain type of ticket 15 15 * to define the table headers displayed in the parent ticket 16 * to define a default for the child type to be created 17 * to restrict the type of child-ticket 18 * to define whether the parent milestone is adopted by child tickets or not 16 * to define a default for the child type to be created / restrict the type of child-tickets 17 * to define which fields are inherited by child-tickets 19 18 20 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. … … 40 39 [childtickets] 41 40 42 # 'enhancements' : child tickets will typically be bug-fix tickets with the same milestone .41 # 'enhancements' : child tickets will typically be bug-fix tickets with the same milestone, component and keywords. 43 42 parent.enhancement.allow_child_tickets = true 44 43 parent.enhancement.restrict_child_type = bug-fix, task 45 44 parent.enhancement.table_headers = type, status, owner, summary 46 parent.enhancement.default_child_type = bug-fix 47 parent.enhancement.inherit_milestone = true 45 parent.enhancement.inherit = milestone, component, keywords 48 46 49 47 # 'bug-report' : child tickets will typically be bug-fix … … 51 49 parent.bug-report.default_child_type = bug-fix 52 50 parent.bug-report.table_headers = type, priority, owner, summary, milestone 53 parent. bug-report.inherit_milestone = false51 parent.enhancement.inherit = component, keywords 54 52 55 53 # 'issue' : child tickets will typically be task tickets with no default milestone. 56 54 parent.issue.allow_child_tickets = true 57 parent.issue. default_child_type = task55 parent.issue.restrict_child_type = task 58 56 parent.issue.table_headers = type, status, owner, summary, milestone 59 parent.issue.inherit_milestone = false60 57 61 58 # 'bug-fix' : child tickets are not allowed. … … 72 69 || parent.<parent-type>.table_headers || List of column headers for display in parent ticket || Default: summary, owner || 73 70 || parent.<parent-type>.default_child_type || Default child type || Default: See [ticket] section of trac.ini (default_type) || 74 || parent.<parent-type>.restrict_child_type || A list of possible child types, trying to create a child of a different 'type' will create an error. || Default: none || 75 || parent.<parent-type>.inherit_milestone || Define whether the child will adopt the parent ticket's milestone || Default: false || 71 || parent.<parent-type>.restrict_child_type || A list of possible child types, trying to create a child of a different 'type' will create an error. As of version 1.1.0, if this option is used, a list of submit buttons will be rendered allowing the user to decide which type of child ticket he/she wants to create. || Default: None || 72 || ~~parent.<parent-type>.inherit_milestone~~ || ~~Define whether the child will adopt the parent ticket's milestone--~~ || THIS OPTION IS NO LONGER AVAILABLE AND HAS BEEN REPLACED WITH THE 'inherit' OPTION BELOW AS OF VERSION 1.1.0 || 73 || parent.<parent-type>.inherit || Define a list of inherited fields. || Default: None || 76 74 77 75 == Issues / Caveats == … … 79 77 * 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. 80 78 * If a parent ticket is restricted in some way that no further child tickets can be generated for that ticket 'type', you'll continue to see a list of child tickets but the 'Create' button will be missing. 79 * The 'parent.type.inherit' option ensures fields ar einherited by child tickets, However, all child tickets (regardless of type as defined by 'restrict_child_type') will inherit these values. 81 80 82 81 == Bugs/Feature Requests == … … 114 113 When developing a new feature (a single ticket), our developers would 'finish' the feature and pass it to our testing department. The feature, on the whole, might be OK but require several days testing. Within that time several bugs are generated as a direct result of this new feature. It makes no sense to pass the original feature ticket back to the developers (the feature has not been 'rejected' and is still in testing!), so instead, the testing tem can make 'bug-fix' child-tickets for this parent ticket. The feature might even be released with known bugs but at least they're recorded and owned by someone/somewhere! 115 114 115 === Using the 'parent.type.restrict_child_type' Option === 116 117 If you are using the above option, the available child types will be rendered as individual buttons. 118 119 [[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/perTypeButtons.png?format=raw)]] 120 116 121 == Recent Changes == 117 122 118 [[ChangeLog(childticketsplugin, 3)]]123 [[ChangeLog(childticketsplugin, 5)]] 119 124 120 125 == Author/Contributors ==