Issues and fields

You will learn what an issue is, what each issue field means, and how issue metadata helps a team decide what to do next.

Issues are the core work records in Tixio. Use them for bugs, tasks, stories, epics, follow-ups, release work, support findings, and anything else that needs an owner, status, context, discussion, or history.

For step-by-step instructions, read Create and manage issues.

Issue keys

Every issue has a key such as TIXI-123. The prefix comes from the project key, and the number increases as issues are created.

Use issue keys in conversations, comments, pull requests, release notes, and status updates. Bare issue keys in descriptions and comments become links, so typing TIXI-123 is often enough to connect related work.

Issue types

Tixio issue types are:

Type	Use it for
Bug	Something is broken or behaving unexpectedly.
Task	A concrete piece of work that does not need story framing.
Story	User-facing or stakeholder-facing work where the outcome matters.
Epic	A larger outcome made up of many issues.

Use the lightest type that communicates intent. A bug should include what is wrong and how to verify the fix. A story should describe the user or business outcome. An epic should describe the larger result, not just collect loose work.

Priority

Priority communicates urgency and importance. Tixio priorities are:

No priority.
Low.
Medium.
High.
Urgent.

Use Urgent only when the team should interrupt planned work. Use High for important work that should be planned soon. Leave No priority when a new issue still needs triage.

Status and resolutions

Each project has its own statuses, grouped into stable categories:

Backlog.
Unstarted.
Started.
Paused.
Completed.
Cancelled.

Status names can vary by project, but the categories drive board columns, filters, reporting, and done checks.

When an issue moves into a done-like status, Tixio may require a resolution such as Fixed, Won't fix, Duplicate, Cannot reproduce, or Obsolete. A resolution explains why the issue is done, especially when no code or product change shipped.

Assignee and creator

The assignee owns the next action. Keep an issue unassigned only when the team has not decided who should pick it up.

The creator is the person who created the issue. Creator is useful for follow-up questions, triage reports, and filters such as work created by a specific teammate.

Use Assign to me when you are taking ownership and want the issue to show up in your personal work views.

Labels

Labels are flexible tags for routing and filtering. Good labels describe stable dimensions such as:

Product area, for example frontend or billing.
Source, for example customer-request.
State, for example needs-triage or blocked.
Work type, for example docs or migration.

Tixio lets you create labels while creating or editing issues. Label colors make busy lists and boards easier to scan, but the name should carry the meaning without relying on color.

Custom fields

Custom fields capture project-specific structured data that does not fit a built-in issue field. A project can define short text, number, date, single-select, and user fields, then show them on matching issue types.

Use custom fields for data that should be consistent, filterable, and visible as table columns. Use labels for looser categories.

For details, read Custom fields.

Dates and estimates

Use Due date when there is a real date commitment, launch date, customer deadline, or time-sensitive follow-up. Avoid using due dates as a generic priority substitute.

Use Estimate when your team plans with story points or relative sizing. Estimates power cycle reports, burndown, burnup, workload, and planning conversations.

For sprint planning context, read Cycles and sprint planning.

Planning fields

Planning fields connect an issue to larger structures:

Cycle places work into a sprint or planning window.
Epic groups work under a larger outcome.
Initiative groups epics under a broader goal.
Milestone groups issues for a date-pinned delivery target.
Fix version and Affects version connect work to releases.

You do not need every field on every issue. Add planning data when it helps the team prioritize, coordinate, report, or ship.

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

Watchers

Watching an issue subscribes you to updates. Tixio automatically subscribes the creator to a new issue, and the comment composer includes a watch option.

Watch issues you own, are blocked by, are mentioned on, or need to follow closely. Stop watching issues when updates no longer need your attention.

For notification behavior, read Notifications.

Attachments and links

Attachments keep evidence close to the work: screenshots, screen recordings, logs, PDFs, CSVs, JSON files, and other supporting files. Image and video files can preview inline.

Issue links describe relationships such as Blocks, Blocked by, Depends on, Causes, Duplicates, Relates to, and subtask relationships.

Comments, mentions and activity

Use comments for decisions, clarifications, handoffs, and updates that should stay with the issue. Use @ mentions when a teammate needs to see the update.

The activity history records important changes so people can understand how the issue got to its current state.

For collaboration notification rules, read Notification event types.