Changes between Version 31 and Version 32 of ChildTicketsPlugin

Timestamp:

Dec 15, 2015, 2:26:52 PM (8 years ago)

Author:

figaro

Comment:

Removal of superfluous trac tag

ChildTicketsPlugin

@@ -11 +11 @@
 It is possible to control in trac.ini the following aspects of child-ticket creation/viewing:
  * allow/disallow child-tickets for a certain type of ticket
- * to define the table headers displayed in the parent ticket
- * to define a default for the child type to be created / restrict the type of child-tickets
- * to define which fields are inherited by child-tickets
+ * define the table headers displayed in the parent ticket
+ * define a default for the child type to be created / restrict the type of child-tickets
+ * define which fields are inherited by child-tickets
 
 === Background
@@ -103 +103 @@
 == Known Issues / Caveats
 
- * 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.
+ * 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.
  * 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.
- * 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.
+ * 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.
 
 == Examples