Changes between Version 26 and Version 27 of SubticketsPlugin
- Timestamp:
- Jan 11, 2017, 9:12:49 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SubticketsPlugin
v26 v27 5 5 == Description 6 6 7 This plugin offers sub-ticket feature for managing tickets. Subtickets are useful for when several tickets are developed and released under one master ticket. The master ticket,in the example below called the Root ticket, has multiple subtickets defined under it.7 This plugin offers a sub-ticket feature for managing tickets. Subtickets are useful for when several tickets are developed and released under one master ticket. The master ticket in the example below called the Root ticket, has multiple subtickets defined under it. 8 8 9 9 The following screenshot demonstrates how the subtickets are displayed below the Description section of a ticket: … … 60 60 # Select column headings in child listing 61 61 # Id and summary are always displayed 62 defect.table_columns = priority,keywords,owner63 t ask.table_columns = # display id and summary only62 type.defect.table_columns = priority,keywords,owner 63 type.task.table_columns = # display id and summary only 64 64 65 65 # Control which fields are inherited from parent to child when creating child 66 defect.child_inherits = keywords,milestone67 t ask.child_inherits = version,cc66 type.defect.child_inherits = keywords,milestone 67 type.task.child_inherits = version,cc 68 68 69 69 # Control the visual appearance of the create subticket link. Config value shall be one of "button" and "link" 70 70 add_style = button 71 72 # Enable ticket modification (except comments) when a parent is closed (default=true) 73 no_modif_when_parent_closed = false 74 75 # Normally SubticketsPlugin will refuse closing parents when a child is non-closed and similarly 76 # reopening a child whose parent is closed. These behaviours can be suppressed by adding 77 # either of the action names tho this setting: 78 skip_closure_validation = resolve,reopen 79 80 # The number of child levels is controlled by the following setting, where 81 # -1 (default) means infinity and zero means one level of children. 82 recursion_depth = 2 # - three levels of children 83 71 84 }}} 85 86 If IniAdminPlugin is installed, the configuration can be edited through the administration panel `subtickets`. The plugin detects which ticket types are defined and creates config values accordingly. Config values are ''not'' deleted when ticket types are deleted and they will disappear from the admin panel only when trac is restarted. Also note that as long as a config value is not changed wrt. its hardcoded default value, it is not added to `trac.ini`. 87 88 === Incompatibilities with earlier versions 89 '''With <= 0.4.1:''' In order to obtain a not-too-unreasonable sorting of config values in the admin panel, all ticket type-specific config values now have the prefix `type.` 72 90 73 91 == Interaction with ticket workflows … … 76 94 * trying to `resolve` a ticket with one or more non-`closed` children 77 95 * trying to `reopen` or modify fields of a `closed` ticket with one or more `closed` parents. 96 97 This behaviour can be inhibited; see above. 78 98 79 99 == About i18n/l10n support