Ticket Tree allows you to categorize your tickets based on the areas affected.
Given this categorization, you can then display the tickets in a tree, getting a better picture
of the areas and sub-areas with more problems.
In addition to that, the tree view lets you navigate your tickets more easily.
The categorization mechanism is really simple, as it's based on the ticket title.
You will use the dash '-' character to define the category and sub-categories in your tickets.
For example, giving the following title to a ticket:
User Interface - Main menu - File menu - Unable to click on the "Open File" item
will display your ticket in the tree as follows:
+ User Interface
+ Main menu
+ File menu
Unable to click on the "Open File" item
For more information, go to the home page on Track-Hacks:
http://trac-hacks.org/wiki/TicketTree
The project source code is hosted on SourceForge.net: http://sourceforge.net/projects/tickettree/
=== Statistics: ===
Next to each category you will see the number of all tickets, and the detail of open and
closed tickets, in that category.
=== Searching and Filtering: ===
You can quickly search and filter tickets in the tree using the "Find" text box.
Just start typing text in it to see your ticket tree reducing and highlighting only the tickets
matching your text.
You can type more than one word: only the tickets matching all of them will be displayed.
Special words are "open" and "closed": they will limit the view to only open and closed tickets,
respectively.
=== Querying: ===
The plugin provides a macro, which lets you build custom ticket trees based on specific ticket
queries.
Used without any parameter, the macro will display a tree with all of the tickets.
=== Simplified categorization: ===
An interesting feature is the ability to open a ticket in a specific category directly from the
tree.
Next to each category you'll find a "new" link, clicking which you will be opened the ticket
creation page with the ticket's title already built with the corresponding category and
sub-categories, and a place-holder for the ticket's short description to follow.
=== Refreshing: ===
The "Refresh" button is useful to perform the query again and update the tree.
Metadata
Release files for TicketTree 0.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tickettree.0.9.src.tar.gz | 6.7 kB | Without provenance | Details for tickettree.0.9.src.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| TicketTree-0.9-py2.5.egg | Legacy Egg format | - | - | Details for TicketTree-0.9-py2.5.egg |
Total release size: 22.7 kB
Release files / tickettree.0.9.src.tar.gz
| Download URL | tickettree.0.9.src.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36d932948c78a6235dabce4199cfd44a696d588a17a083bd1c5e194554063af9
|
|
BLAKE2b-256 checksum How to use checksums |
3da58914c1bec975b512b93a82b2294cc357ac942d712703f8eeed503821a01b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / TicketTree-0.9-py2.5.egg
| Download URL | TicketTree-0.9-py2.5.egg |
|---|---|
| Size | 16.1 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
5260f886385673b634c4cc9be3df8b70a69d60bab610b906994ba61e9f2f13bd
|
|
BLAKE2b-256 checksum How to use checksums |
61c1afbea79185352dee8caf5e5746b9010f613357606eaa9bab9c5849d1770f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TicketTree 0.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.