Skip to content

Concepts

You will learn the core building blocks that appear throughout Tixio.

This page is a compact map of the terms you will see first. Use the deeper concept pages below when you need the full model for an area.

Deeper concept pages

  • Accounts and security explains account identity, sign-in methods, sessions, password requirements, MFA, profile photos, SSO, and invitation routing.
  • API keys and programmatic access explains personal keys, service accounts, scopes, rotation grace, audit, and security practices for MCP and REST clients.
  • Workspaces, projects and members explains workspace/project structure, visibility, roles, invitations, and archived projects.
  • Issues and fields explains issue keys, types, priorities, statuses, resolutions, assignees, labels, planning fields, watchers, attachments, relationships, comments, and activity.
  • Custom fields explains project-specific field definitions, supported types, issue values, table columns, filters, archive, and delete behavior.
  • Issue views, dashboards and analytics explains list, board, table, calendar, timeline, backlog, dashboards, Insights, and when to use each.
  • Cycles and sprint planning explains cycle states, sprint scope, capacity, commitment snapshots, carry-over, filters, and reopening.
  • Sprint reports and charts explains Sprint Reports, committed work, scope changes, burnup, burndown, and velocity.
  • Epics, initiatives, milestones and versions explains planning hierarchy, issue-to-epic nesting, initiatives, milestones, versions, fix versions, and affects versions.
  • Epic and initiative rollups explains epic lists, project filters, No epic rollups, progress bars, child issue filters, initiative detail, and History.
  • Search, saved views and My Work explains command search, project filters, saved views, cross-project views, My Work, and triage signals.
  • Notifications explains the bell, Inbox, notification event types, delivery channels, digests, Slack delivery, and mutes.
  • AI assistant and chat explains in-app Ask AI, assistant capabilities, read/write safeguards, Slack chat, AI limits, and audit visibility.

Workspace

A workspace is the top-level home for a team or organization. It contains members, projects, saved views, dashboards, settings, integrations, notifications, and administration.

Use one workspace when the same organization should share membership and data. Use separate workspaces only when access, data boundaries, or administration really need to be separate.

Project

A project is a focused stream of work inside a workspace. Projects have their own issue keys, issue views, backlog, cycles, versions, dashboards, automation, members, and settings.

Use a project when a team, product area, or service needs its own queue and reporting. Keep the first few projects broad enough that people know where work belongs.

Issue

An issue is a unit of work. It can represent a bug, task, story, or epic. Issues carry status, priority, assignee, creator, labels, due dates, estimates, comments, attachments, links, activity history, and planning fields.

Create an issue when something needs an owner, discussion, history, or visible status.

Label

A label is lightweight grouping. Labels are useful for dimensions that do not belong in a single field, such as frontend, customer-request, needs-triage, or docs.

Use labels sparingly. Too many labels make filtering harder instead of easier.

Cycle

A cycle is a sprint or planning window. It groups issues the team intends to work on during a period of time. Cycles help with scope, carry-over, burndown, burnup, and sprint reporting.

Use cycles when your team plans in time boxes. If your team works as a pure continuous flow, you can rely on backlog, statuses, and saved views instead.

For details, read Cycles and sprint planning.

Epic

An epic groups many issues under a larger outcome. Use epics when progress should roll up across multiple issues, teams, or projects.

Good epics describe an outcome, not just a folder. For example, "User guide documentation" is more useful than "Docs tasks."

For details, read Epics, initiatives, milestones and versions.

Milestone and version

Milestones and versions group work for a release, launch, or date. Use them when the important question is "what needs to ship together?"

Versions are especially helpful when you track fix versions and affects versions for product releases.

For release planning, read Plan releases with milestones and versions.

View

A view is a saved issue query and surface. Views help you return to useful slices of work such as "my open issues", "active cycle bugs", or "unassigned work across projects."

Views can open in surfaces such as list, board, table, calendar, or timeline depending on what you are trying to understand.

For details, read Search, saved views and My Work.

Dashboard

A dashboard collects widgets, charts, and rollups. Use dashboards when a team or lead needs a standing status page instead of repeatedly rebuilding filters.

Notification

A notification is a personal update about work that may need attention. Notifications can appear in the bell, Inbox, email, or Slack depending on your settings.

For details, read Notifications.

AI assistant

The AI assistant helps you search, summarize, and act on Tixio work from natural-language chat. It can use workspace and project context, show tool cards, and ask for confirmation before write actions in the app.

For details, read AI assistant and chat.

Learn more

For a new-user path, start with What is Tixio?. For a product tour, use Five-minute tour.