Operating manual
Projects and ticket continuity
Organise a substantial request while preserving its origin and conversation.
Before you begin
- Projects enabled and operational department access.
Step by step
Search existing projects before creating one.
Create a standalone project or promote a ticket with required data, estimate and dates.
Check the original ticket link and connect other relevant requests.
Organise tasks, assignments and time; advance workflow and archive when no longer needed in current work.
Distinguish tasks, subtasks and milestones: a milestone represents a checkpoint rather than a work estimate. Check dates, assignee and status before saving, and use project attachments for shared materials.
Archiving and restoring are separate from completing a project. To find an archived project enable Include archived in the list, inspect filters and select Restore.
The result to check
The project preserves the ticket and keeps navigable links.
Limits and considerations
- Workflow and archive depend on capability and version.
- Use summaries to avoid counting direct and task time twice.
Continue with related guides
Break down delivery and retain a plan snapshot.
↗PlanningGlobal planning and forecastsRead tickets, projects and tasks without counting containers twice.
↗TimeTimers and manual entriesRecord tickets, projects, tasks and external activities.
↗THE NEXT STEP
Keep following the thread.
Explore the tools or compare plans for your team.