Version 40 (modified by Greg Troxel, 5 years ago) (diff)

note that pgsql 84 works

Add support for ticket dependencies to Trac


What is it?

This plugin adds "blocks" and "blocked by" fields to each ticket, enabling you to express dependencies between tickets. It also provides a graphviz-based dependency-graph feature for those tickets having dependencies specified, allowing you to visually understand the dependency tree. The dependency graph is viewable by clicking 'depgraph' in the context (in the upper right corner) menu when viewing a ticket that blocks or is blocked by another ticket.

This plugin works on Trac 0.11 (no longer maintained), Trac 0.12 and Trac 1.0.

Shows "Depgraph" link on ticket (#62). This ticket has dependencies shown grafically.

Shown on screen shot:

  1. "Depgraph" link at ticket #62 (on middle top, yellow bullet);
  2. Blocks and blocked by extra fields at ticket #62;
  3. graphical representation and deeper relation to other tickets (on right);
  4. ticket statuses explanation (lower left corner).

What is it not?

  • It does not provide ticket-hiding for sub-tasks of a top-level ticket.
    • There is no parent/child relationship possible (though this is now on the roadmap for an upcoming release, see #10964).
    • You cannot view the descriptions of tickets depending on the current ticket.
    • In fact, there are no explicit features that can assist you with sub-task management.
    • Although it would be cool.
  • It does not allow you to create a dependent ticket from the current ticket
  • It does not include reporting features to show how tasks are interrelated (other than the dependency graph already described above).

Just put the ticket numbers that a given ticket is blocking in the Blocking field. Enter just the number, no leading #. Separate multiple numbers with commas.

Make sure you add the custom fields as shown below.

You need to install graphviz to use the dependency graphs. You do not need the GraphvizPlugin or anything else beyond the dot binary.

Bugs/Feature Requests

Existing bugs and feature requests for MasterTicketsPlugin are here.

If you have any issues, create a new ticket.




Download the latest revision from [download:masterticketsplugin here].

There is an unofficial Debian package. To rebuild this package from scratch you need the package source which extracts the revision b8715f528a from github.


You can check out MasterTicketsPlugin from here using Subversion, or browse the source with Trac.


To enable, add to trac.ini:

mastertickets.* = enabled

blocking = text
blocking.label = Blocking
blockedby = text
blockedby.label = Blocked By

Under the mastertickets section the following options are available:

  • dot_path (default='dot'): Path to the dot executable
  • gs_path (default='gs'): Path to the ghostscript executable
  • use_gs (default=False): If enabled, use ghostscript to produce nicer output

To configure the plugin to use a graphviz/dot installation that is at another location:


Upgrade your installation

After installing or enabling this plugin, trac will claim that it needs to be upgraded; this is because the plugin adds a new table to the database. So run:

trac-admin /path/to/env upgrade

Known acceptable database versions

Sometimes trac and/or plugins run into trouble with newer database versions because they are fussier about error checking. Therefore this section lists versions that are known to work.

  • 3.0.4: postgresql 8.4, trac 1.0.1, python 2.7

Recent Changes

17147 by rjollos on 2018-04-23 15:22:28
TracMasterTickets 4.0.2: Release version 4.0.2
17048 by rjollos on 2018-03-03 06:35:43
TracMasterTickets 4.0.2dev: Add compatibility with Trac 1.3dev

Fixes #13381.

16813 by rjollos on 2017-09-13 21:42:24
TracMasterTickets 4.0.2dev: Print commands as string rather than list

Refs #12658.



Author: coderanger
Maintainer: rjollos, Apache Bloodhound team
Contributors: mitar