Changes between Version 3 and Version 4 of TracRelationsPlugin


Ignore:
Timestamp:
Apr 16, 2021, 9:39:39 PM (2 months ago)
Author:
Cinc-th
Comment:

Added some more feature description and section about other dependency plugins.

Legend:

Unmodified
Added
Removed
Modified
  • TracRelationsPlugin

    v3 v4  
    77This plugin provides a general system for relating different Trac resources. The kind of resource is dependend on the use case.
    88
    9 It comes with plugins for relations between tickets with the following. features:
     9It comes with plugins for relations between tickets with the following **link types**:
    1010* simple relations between tickets without any special semantics ({{{relates to}}})
    1111* allow a ticket to {{{block}}} another ticket
     
    1313* {{{duplicate}}} tickets
    1414
     15The relations are saved in the database and can be used in reports.
    1516
    16 Features:
     17=== Enhanced ticket page
    1718* The plugin adds the relationship information to the ticket properties box when a ticket page is shown.
    18 * Manage relations between tickets from the ticket page.
    19 * For {{{blocked}}} tickets the plugin makes sure that a ticket can't be resolved as long as any blocking ticket is still open.
     19* Manage relations between tickets from the ticket page using a popup dialog.
     20* Buttons for direct creation of child tickets of different types.
    2021* When child tickets exist for a ticket they are shown as a tree below the properties box.
    21 * When resolving a ticket as a duplicate the user may input a ticket number and a {{{duplicate}}} relation is automatically created.
    2222
    23 === Screenshots
     23=== Duplicate tickets
     24When resolving a ticket as a duplicate the user may input a ticket number and a {{{duplicate}}} relation is automatically created.
     25
     26
     27=== Blocking tickets
     28Ticket validator checks for {{{blocked}}} tickets:
     29  * Disallowing closing of a ticket when open blocking tickets exist
     30  * Detecting loops in your dependencies
     31  * Making sure a blocked or blocking ticket actually exists
     32
     33=== Child tickets
     34
     35* Child tickets may have one or several parents
     36* Show a child ticket tree with proper indentation and configurable depth
     37* Ticket validator checks for:
     38  * Disallowing closing of parents when open children exist
     39  * Detecting loops in your dependencies
     40  * Making sure a parent ticket actually exists
     41* Allow/disallow child-tickets for a certain type of ticket
     42* Define the table headers displayed in the child ticket depending on the type
     43* Define a default for the child type to be created
     44* Restrict the type of possible child-tickets for each parent ticket type
     45* Define which fields are inherited by child-tickets
     46
     47There are admin pages available for configuring the features but it is also possible to control them by settings in trac.ini. See the configuration section for more info.
     48
     49=== Other plugins
     50
     51[[ListTagged(dependency plugin)]]
     52
     53== Screenshots
    2454{{{#!box width=500
    2555==== Relation properties