Conditionally set ticket creation status

Notice: This plugin is deprecated with Trac 1.1.3 or later (trac:#2045) since Trac allows ticket create actions to be defined.


This plugin is an evolution of the TicketCreationStatusPlugin, permitting conditioned setting of creation status, depending on arbitrary ticket field values, e.g. type.

Status can be chosen independently for owned or unowned tickets.

This plugin is sponsored by Yalwa Branchenbuch.

Bugs/Feature Requests

Existing bugs and feature requests for TicketConditionalCreationStatusPlugin are here.

If you have any issues, create a new ticket.


Download the zipped source from here.


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


General instructions on installing Trac plugins can be found on the TracPlugins page.

Activate the component in your trac.ini file like this:

ticketconditionalcreationstatus.* = enabled

Configuration is then written in a separate section, headed [ticketconditionalcreationstatus]. There is one fixed configuration variable, criteria, taking as value a list of ticket field names that you want to use as conditions.

For any of the criteria you can then write variables <fieldname>.owned or <fieldname>.unowned:

  • in the simplest form, such a variable takes the form <fieldcontent> -> <ticketstatus>
  • you can also give several such rules, like <content1> -> <status1>, <content2> -> <status2>
  • when you have several content values that should map to the same status, you can use <content1>|<content2> -> <status>


The following example will make owned tickets of types task and task-dev start out as assigned, instead of new, and tickets of type plan start out as new_plan:

criteria = type
type.owned = task|task-dev -> assigned, plan -> new_plan

Recent Changes

10491 by bof on 2011-07-22 20:01:04
operate like on ticket creation when existing ticket goes from closed to new. and some TAB->space fixes.
10356 by bof on 2011-06-21 12:23:16
fix bad import in init
10355 by bof on 2011-06-21 09:32:59
expand configuration: comma separated list of cond->value, and multiple cond1|cond2|...


Author: bof
Maintainer: Patrick Schaaf

Last modified 7 years ago Last modified on May 14, 2017, 3:40:01 PM