31 | | If upgrading from Trac 0.10, you will need to convert the data using the `migrate_pending_attrib_to_status.py /path/to/tracenv` script which is included. |
32 | | |
33 | | Set up your ticket workflow to include a 'pending' status, for example in your `trac.ini` file: |
34 | | {{{#!ini |
35 | | [ticket-workflow] |
36 | | pending = new -> pending |
37 | | pending.permissions = TICKET_MODIFY |
38 | | }}} |
39 | | |
40 | | Specify a status for tickets that it needs to be moved to: |
41 | | {{{#!ini |
42 | | [ticket] |
43 | | pending_removal_status = new |
44 | | }}} |
45 | | |
46 | | Install the !PendingStatusRemovePlugin to have the pending flag automatically removed when the reporter responds: |
47 | | {{{#!sh |
48 | | <CHECKOUT THE SOURCE AND GO TO THE ../removependingplugin DIRECTORY> |
49 | | setup.py bdist_egg |
50 | | cp dist/RemovePendingStatusPlugin-x-y-z-py2.4.egg $TRAC_ENV/plugins |
51 | | }}} |
| 31 | General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page. |
59 | | To enable the automatic closing of tickets, you'll need to set up a script to be run by cron. Mine looks like this: |
| 39 | Set up your ticket workflow to include a 'pending' status, for example in your `trac.ini` file: |
| 40 | {{{#!ini |
| 41 | [ticket-workflow] |
| 42 | pending = new,assigned,accepted,reopened -> pending |
| 43 | pending.permissions = TICKET_MODIFY |
| 44 | }}} |
| 45 | |
| 46 | Specify the status for tickets when 'pending' is removed: |
| 47 | {{{#!ini |
| 48 | [ticket] |
| 49 | pending_removal_status = new |
| 50 | }}} |
| 51 | |
| 52 | To enable the automatic closing of tickets, you'll need to set up a script to be run by cron. |