Changes between Version 9 and Version 10 of ChildTicketsPlugin


Ignore:
Timestamp:
Feb 12, 2011 12:11:27 PM (4 years ago)
Author:
walnut
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ChildTicketsPlugin

    v9 v10  
    1414 * allow/disallow child-tickets for a certain type of ticket 
    1515 * 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 
    1918 
    2019Under 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. 
     
    4039[childtickets] 
    4140 
    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. 
    4342parent.enhancement.allow_child_tickets = true 
    4443parent.enhancement.restrict_child_type = bug-fix, task 
    4544parent.enhancement.table_headers = type, status, owner, summary 
    46 parent.enhancement.default_child_type = bug-fix 
    47 parent.enhancement.inherit_milestone = true 
     45parent.enhancement.inherit = milestone, component, keywords 
    4846 
    4947# 'bug-report' : child tickets will typically be bug-fix 
     
    5149parent.bug-report.default_child_type = bug-fix 
    5250parent.bug-report.table_headers = type, priority, owner, summary, milestone 
    53 parent.bug-report.inherit_milestone = false 
     51parent.enhancement.inherit = component, keywords 
    5452 
    5553# 'issue' : child tickets will typically be task tickets with no default milestone. 
    5654parent.issue.allow_child_tickets = true 
    57 parent.issue.default_child_type = task 
     55parent.issue.restrict_child_type = task 
    5856parent.issue.table_headers = type, status, owner, summary, milestone 
    59 parent.issue.inherit_milestone = false 
    6057 
    6158# 'bug-fix' : child tickets are not allowed. 
     
    7269|| parent.<parent-type>.table_headers || List of column headers for display in parent ticket || Default: summary, owner || 
    7370|| 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 || 
    7674 
    7775== Issues / Caveats == 
     
    7977 * 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. 
    8078 * 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. 
    8180 
    8281== Bugs/Feature Requests ==  
     
    114113When 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! 
    115114 
     115=== Using the 'parent.type.restrict_child_type' Option === 
     116 
     117If 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 
    116121== Recent Changes == 
    117122 
    118 [[ChangeLog(childticketsplugin, 3)]] 
     123[[ChangeLog(childticketsplugin, 5)]] 
    119124 
    120125== Author/Contributors ==