6 | | This plugin allows you to define checklists as a wiki page, and then embed them in tickets as templates for recurring tasks. This prevents people from forgetting something (e.g. tag a new version), and allows for ongoing process improvements by updating the checklist whenever gaps in the existing process are discovered. |
| 6 | This plugin allows you to define checklists as a wiki page, and then embed |
| 7 | them in tickets as templates for recurring tasks. For example, if your workflow |
| 8 | for a bug ticket includes steps for fix/test/release, each of these can be defined |
| 9 | as a step and checked off as the assignee works on the ticket. |
| 10 | |
| 11 | This prevents people from forgetting something (e.g. tag a new version), and |
| 12 | allows for ongoing process improvements by updating the checklist whenever gaps |
| 13 | in the existing process are discovered. |
| 18 | ---- |
| 19 | |
| 20 | == Install |
| 21 | |
| 22 | A plugin can either be deployed globally, or only for a specific environment. |
| 23 | Global deployment is done by installing the plugin: |
| 24 | {{{ |
| 25 | $ cd /path/to/pluginsource |
| 26 | $ python setup.py install |
| 27 | }}} |
| 28 | |
| 29 | The plugin is also available on PyPI and can be installed globally using pip: |
| 30 | {{{ |
| 31 | $ pip install TracChecklist |
| 32 | }}} |
| 33 | |
| 34 | To deploy a plugin only to a specific Trac environment, copy the egg file into |
| 35 | the plugins directory of that environment: |
| 36 | {{{ |
| 37 | $ cd /path/to/pluginsource |
| 38 | $ python setup.py bdist_egg |
| 39 | $ cp dist/*.egg /path/to/projenv/plugins |
| 40 | }}} |
| 41 | |
| 42 | == Setup |
| 43 | |
| 44 | The plugin requires a new database table; update the environment to create it: |
| 45 | {{{ |
| 46 | $ trac-admin /path/to/env upgrade |
| 47 | }}} |
| 48 | |
| 49 | The plugin uses static resources (CSS, JS). If you mapped static resources so |
| 50 | they are served by the web server, the resources need to be deployed to the |
| 51 | location on the filesystem that is served by the web server. Execute the deploy |
| 52 | command, as is done during install and upgrade: |
| 53 | {{{ |
| 54 | $ trac-admin /path/to/env deploy /deploy/path |
| 55 | }}} |
| 56 | |
| 57 | The plugin creates a {{{wiki:ChecklistTemplates}}} page as the {{{root}}} below which all |
| 58 | checklist definitions are located. If you move the page, update the entry in your |
| 59 | {{{trac.ini}}} file: |
| 60 | {{{ |
| 61 | [checklist] |
| 62 | template_root = /path/to/ChecklistTemplates |
| 63 | }}} |
| 64 | |
| 65 | Restart the server once fully configured. |
| 66 | |
14 | | Create at least one checklist as a sub-page below the {{{ChecklistTemplate}}} wiki page using the provided template. You can create pages below non-existing parents, which will be treated as category headers. For example: |
| 70 | Create at least one checklist as a sub-page below the {{{wiki:ChecklistTemplates}}} page |
| 71 | using the template provided. You can also create pages below non-existing parents, which |
| 72 | will then be treated as category headers. For exmaple: |
| 73 | {{{ |
| 74 | wiki:ChecklistTemplates |
| 75 | |- CatOne (not a page) |
| 76 | |- wiki:ChecklistTemplates/CatOne/Checklist One |
| 77 | |- wiki:ChecklistTemplates/CatOne/Checklist Two |
| 78 | |- CatTwo (not a page) |
| 79 | |- wiki:ChecklistTemplates/CatTwo/Checklist Three |
| 80 | |- wiki:ChecklistTemplates/CatTwo/Checklist Four |
| 81 | }}} |