Changes between Version 26 and Version 27 of SubticketsPlugin


Ignore:
Timestamp:
Jan 11, 2017, 9:12:49 PM (9 months ago)
Author:
Theodor Norup
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SubticketsPlugin

    v26 v27  
    55== Description
    66
    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.
     7This 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.
    88
    99The following screenshot demonstrates how the subtickets are displayed below the Description section of a ticket:
     
    6060# Select column headings in child listing
    6161# Id and summary are always displayed
    62 defect.table_columns = priority,keywords,owner
    63 task.table_columns   = # display id and summary only
     62type.defect.table_columns = priority,keywords,owner
     63type.task.table_columns   = # display id and summary only
    6464
    6565# Control which fields are inherited from parent to child when creating child
    66 defect.child_inherits = keywords,milestone
    67 task.child_inherits   = version,cc
     66type.defect.child_inherits = keywords,milestone
     67type.task.child_inherits   = version,cc
    6868
    6969# Control the visual appearance of the create subticket link. Config value shall be one of "button" and "link"
    7070add_style = button
     71
     72# Enable ticket modification (except comments) when a parent is closed (default=true)
     73no_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:
     78skip_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.
     82recursion_depth = 2    # - three levels of children
     83
    7184}}}
     85
     86If 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.`
    7290
    7391== Interaction with ticket workflows
     
    7694 * trying to `resolve` a ticket with one or more non-`closed` children
    7795 * trying to `reopen` or modify fields of a `closed` ticket with one or more `closed` parents.
     96
     97This behaviour can be inhibited; see above.
    7898
    7999== About i18n/l10n support