Workflows

You will learn practical routines for turning Tixio from an empty workspace into a team habit.

Use this page as the starting playbook for common team motions, then open the dedicated workflow guides for step-by-step detail.

Setup and access workflows

• Sign up, sign in and sessions covers account creation, email verification, Google, SSO, MFA sign-in, invitations, and the workspace picker.
• Manage account security covers profile photos, password changes, email changes, MFA setup, recovery codes, and disabling MFA.
• Manage API keys and service accounts covers personal API keys, MCP setup for Cursor and Claude Desktop, REST X-API-Key usage, key rotation, and service account administration.
• Set up workspaces and projects covers workspace creation, workspace rename, project creation, project visibility, project settings, archive, and restore.
• Manage members and access covers workspace invites, project access, roles, pending invitations, and access troubleshooting.
• Create and manage issues covers new issues, issue fields, ownership, labels, status changes, due dates, estimates, clone, delete, and triage.
• Use issue detail and collaboration covers issue tabs, collaborative descriptions and comments, attachments, relationships, watchers, mentions, activity, and revision history.
• Manage project custom fields covers custom field creation, editing, archive, reorder, issue values, table columns, and filters.
• Use issue views and backlog covers list, board, table, calendar, timeline, backlog, filters, display options, and bulk edit.
• Use dashboards and insights covers project Insights, triage, velocity, burnup, burndown, cycle time, workload, Sprint Reports, and custom dashboards.
• Plan and run a sprint covers cycle creation, scope selection, estimates, starting a sprint, active sprint monitoring, and mid-sprint scope changes.
• Close and review a sprint covers carry-over, reopening closed cycles, Sprint Reports, burnup, burndown, and velocity review.
• Manage epics and initiatives covers epic creation, issue assignment, Epics list controls, No epic cleanup, initiative creation, and adding/removing epics from initiatives.
• Plan releases with milestones and versions covers milestones, target dates, project versions, fix versions, affects versions, shipping milestones, and releasing versions.
• Find work with search and filters covers command search, project filters, query examples, My Work, and triage cleanup.
• Create and share saved views covers saved view creation, visibility, Order By, surfaces, cross-project board/table behavior, editing, and maintenance.
• Review and manage notifications covers the bell, Inbox, read/archive state, project grouping, click-through, and inbox review routines.
• Tune notification settings covers in-app, email, Slack, digest timing, Slack requirements, and project/issue mutes.
• Chat with the AI assistant covers Ask AI, chat composer behavior, slash commands, proactive prompts, tool cards, plans, and write confirmations.
• Use the Slack AI assistant covers Slack DM chat, channel mentions, thread follow-ups, read-only behavior, and Slack table rendering.

Capture work

Use issues for work that needs an owner, status, context, or history.

A practical capture routine:

1. Create the issue in the project where the work will be owned.
2. Write a specific title that can stand alone in a list or board.
3. Add enough description for someone else to act without asking for the original context.
4. Set type, priority, assignee, and labels when they are known.
5. Leave unclear work in a triage status or backlog until someone confirms the next action.

Use labels such as needs-triage, customer-request, or blocked only when they help people find or route work.

Triage a backlog

Backlog triage is the habit of turning raw work into actionable work.

For each issue, decide:

• Is this real work, a duplicate, or no longer needed?
• Does the title describe the outcome?
• Is the description clear enough?
• Who owns the next action?
• Does it need a priority, estimate, due date, label, cycle, epic, milestone, or version?

Do not overfill fields just because they exist. Add planning data when it helps someone decide what to do next.

Plan a cycle

Use cycles when your team works in sprints.

For a full cycle workflow, read Plan and run a sprint and Close and review a sprint.

Before starting a cycle:

1. Review candidate issues in the backlog or a saved planning view.
2. Confirm each issue has enough context and an owner or expected owner.
3. Estimate the work if your team uses points.
4. Move the committed issues into the planned cycle.
5. Start the cycle when the team agrees on scope.

During the cycle, watch for added work, removed work, and estimate changes so the sprint report tells the real story.

Run daily standup

Standup works best when the view already answers "what changed?"

Use a saved view or project surface filtered to:

• Issues assigned to the current team or person.
• Work in the active cycle.
• Blocked or high-priority work.
• Items changed since the last standup.

Ask each person to update status, add a short comment when context changed, and flag blockers where the team can see them.

For reusable queues, read Create and share saved views.

Break down an epic

Use an epic for an outcome that needs multiple issues.

A practical epic breakdown:

1. Write the outcome and acceptance criteria in the epic.
2. Create child issues for independently shippable parts.
3. Assign each issue to the right project and owner.
4. Use labels, cycles, milestones, or versions only where they help planning.
5. Review epic progress by status and remaining points.

Keep epics outcome-focused. If an epic is only a parking lot, it will be hard to know when it is done.

For a full workflow, read Manage epics and initiatives.

Ship a milestone

Use milestones or versions when multiple issues need to ship together.

A release routine:

1. Create the milestone or version.
2. Attach the issues that must ship.
3. Review open blockers in a saved view or table.
4. Confirm fixed issues, known issues, and carry-over.
5. Release the version or close the milestone when the work ships.

For a full workflow, read Plan releases with milestones and versions.

Reduce manual work

Use saved views, dashboards, automation, notifications, integrations, and the AI assistant after the basic process is working.

Good first automations are small:

• Notify watchers when a high-priority issue is created.
• Update watchers or labels when a status changes.
• Connect GitHub or GitLab activity to the relevant issue.

Avoid automating a process the team has not agreed on yet. Automation should make a stable habit cheaper, not hide confusion.

For the full integrations section, start at Integrations and automation. Dedicated guides cover automation rules, webhooks, GitHub, Slack, and MCP and the API.

For notification tuning, read Tune notification settings. For assistant workflows, read Chat with the AI assistant.

Learn more

If you are still setting up, finish Set up your workspace and Invite your team first.