A task collects tickets into a project work package with its own assignment and progress. A ticket can belong to a task or directly to a project. Both can be assigned to project members.
Create and assign work
- Open Tickets and create a task or ticket, or open an existing one.
- Choose the project and assigned project member. For a ticket, choose a parent task if needed.
- Enter a title and description. Set a due date, priority and progress where useful. Tickets also offer difficulty.
- Save and check the assignment.
Priority indicates urgency. Difficulty describes how demanding a ticket is; neither is an hours estimate. Set up project participation first if the required person is unavailable.
Ticket permissions have separate read and write levels for all project tickets and assigned or subscribed work. A subscription does not grant unrestricted project access. Host grants cap access on shared projects, including for guest administrators.
Completion and progress
Expand a task to see its tickets. In the task’s progress selector, choose a percentage for manual tracking or Auto to calculate it from tickets. Automatic progress includes partial progress on open tickets and has no percentage when there are no tickets. The displayed label identifies the method.
Use Complete when finished and Reopen when work resumes. Completing a task can close its tickets too; use the separate option to complete the task while keeping tickets open.
Completion differs from budgets and quotas, which compare recorded work or income with target amounts.
Record work from a ticket
Open the ticket and select its time-recording action. It prepares a Mikron, the saved time record used by Treetops, with the ticket assignment.
Choose the category, check the date, start and end times, then save. Starting from a ticket does not itself save worked time. The time recording guide covers entry, drafts and review.
Projects can require an active task on new time records. A ticket under an active task supplies it; a ticket directly under the project does not.
Comments, labels and files
Use the ticket’s description for the work details and comments for discussion. Reactions provide short responses to comments. Project labels group related tickets and can help filter work.
Add supporting files in the ticket’s attachment area. Each file may be at most 25 MiB. Downloads require access to the ticket.
Subscriptions and notifications
Use Subscriptions to follow task or ticket changes and manage participants where permitted. Assignment is separate from subscription.
Subscribers receive email when a ticket or task is created, changed, closed or reopened, and when someone comments on a ticket. Treetops does not email you about your own actions. Commenting on a ticket subscribes you to it.
A member assigned when a ticket or task is created receives a separate assignment email. Assigning someone during a later edit sends no assignment email. Due-work reminders go to subscribers for work due the next day.
Select Small change to suppress subscriber email for that edit. It does not apply to closing or reopening.
Saving an edit does not confirm email delivery. Contact Gorilla Computing when expected notices are missing.
Pins, filters and completed work
Use a ticket’s star to pin it. Pinned tickets appear before unpinned tickets within their project or task list.
Filter by project, task, ticket or assigned member. Saved filters retain selections; quick search narrows visible work. Sort by due date, priority, difficulty, progress, name or creation and update dates.
Use the archive view for completed work. Ticket charts summarize priority, difficulty and overdue status by project or label.