Skip to content

What is Tixio?

You will learn the mental model behind Tixio so the rest of the app feels predictable.

Tixio is work tracking for teams that need more than a simple task list but do not want planning, status, and context spread across many tools. It combines issue tracking, sprint planning, list and board views, dashboards, saved views, notifications, integrations, and an AI assistant in one workspace.

The mental model

Think of Tixio as a set of nested scopes:

  1. A workspace contains your organization or team.
  2. A project contains a focused stream of work inside that workspace.
  3. An issue is a single unit of work in a project.
  4. A cycle groups issues for a sprint or time-boxed planning window.
  5. An epic groups a larger initiative, often across many issues.
  6. A milestone or version groups work for a date-pinned release.
  7. A view saves a useful slice of issues so you can return to it.
  8. A dashboard shows rollups and charts for work you want to monitor.

You do not need to use every layer on day one. Most teams start with one workspace, one or two projects, and issues. Cycles, epics, milestones, saved views, and dashboards become useful once the project has enough work to need planning and reporting.

Workspaces

A workspace is the boundary for people, settings, integrations, saved views, notifications, and workspace-level administration. Most companies use one workspace. Larger organizations may use separate workspaces when teams need separate membership, data, or integration boundaries.

Use workspace settings for:

  • Inviting and managing members.
  • Switching or reviewing workspace-wide settings.
  • Connecting integrations such as Slack, GitHub, Jira, webhooks, API keys, SSO, and data portability when your plan supports them.
  • Reviewing workspace-level notifications and audit history when available.
  • Setting AI assistant token limits and reviewing assistant usage when available.

Projects

A project is where day-to-day work happens. Each project has its own issue key, issue surfaces, backlog, cycles, versions, dashboards, automation, members, and settings.

Use projects to separate work that has different owners, workflows, or reporting needs. For example, one workspace might contain Product, Platform, and Website projects.

When you create a project, you choose:

  • A project name.
  • An optional description.
  • Visibility: Private for invite-only access or Team for workspace members.
  • The URL short name and issue key prefix, if the defaults need adjustment.

Issues

Issues are the core records in Tixio. Use an issue for a bug, task, story, or epic-sized item that someone needs to track.

An issue usually has:

  • A key, such as TIXI-123.
  • A title and description.
  • A type, priority, status, assignee, creator, labels, due date, estimate, cycle, epic, milestone, and versions as needed.
  • Comments, attachments, links, and activity history.

Keep issue titles specific enough to scan in a list or board. Use the description for context, acceptance criteria, screenshots, reproduction steps, or decisions that should travel with the work.

Cycles

Cycles are sprint-like planning windows. Use them when your team commits to a set of issues for a period of time and wants to track scope, carry-over, and completion.

Common cycle habits:

  • Keep the next cycle planned but not started until the team agrees on scope.
  • Move only actionable issues into the active cycle.
  • Review burndown, burnup, and sprint reports during or after the cycle.
  • Close the cycle deliberately so unfinished work is handled consistently.

Epics, milestones, and versions

Use an epic when many issues contribute to one larger outcome, especially when the work spans projects or needs progress rollup. Use milestones or versions when the important question is "what ships by this date or release?"

Examples:

  • Epic: "User guide documentation" across docs setup, content, screenshots, and deployment tasks.
  • Milestone: "June launch" with date-pinned launch work.
  • Version: v2.4 with fix versions and affects versions for release tracking.

Views and dashboards

Views save a slice of work, such as "my open bugs", "active cycle work across projects", or "unassigned issues created this week." Views can open as list, board, table, calendar, or timeline depending on the surface that best fits the question.

Dashboards are for monitoring. Use them when you want charts, counts, or project-level rollups without rebuilding a filter every time.

AI assistant

The AI assistant helps you ask natural-language questions about Tixio work. Use it to search, summarize, generate status reports, triage My Work, and prepare controlled changes. In the app, write actions require confirmation before they run. In Slack, the assistant answers questions but does not make changes.

For details, read AI assistant and chat.

How to decide what to use

Start small:

  • Use issues for work that needs an owner, status, discussion, or history.
  • Use labels for lightweight grouping that can cross types and priorities.
  • Use cycles when the team plans a time-boxed sprint.
  • Use epics when a larger outcome needs progress rollup.
  • Use milestones or versions when date or release tracking matters.
  • Use views when you repeat the same filter often.
  • Use dashboards when you need an at-a-glance status page.

Next

Continue to Set up your workspace.