Create and manage issues

You will learn how to create your first issue, set the right fields, update it as work changes, and avoid common issue-management mistakes.

For field definitions, read Issues and fields.

Create an issue

Open a project and choose New issue.

Fill in:

Title: write the outcome or problem in one scannable sentence.
Description: add context, acceptance criteria, reproduction steps, screenshots, links, or decisions.
Type: Bug, Task, Story, or Epic.
Priority: No priority, Low, Medium, High, or Urgent.
Status: the first project status is selected by default.
Assignee: leave unassigned for triage or choose the owner.
Labels: add existing labels or create new labels when needed.
Cycle: choose Backlog, an active cycle, or a planned cycle.
Due date and Estimate when they help planning.
Epic or Initiative when the issue belongs to larger work.

Select Create issue. Tixio shows a confirmation with a link to open the new issue.

Write a useful title

A good title should make sense in a list, board card, notification, or search result.

Good examples:

"Import CSV preserves labels with spaces"
"Add billing owner to workspace invite email"
"Fix board card jump after status drag"

Avoid titles such as "Bug", "Fix issue", or "Dashboard work". Put background details in the description instead.

Use the description well

Use the description for information that should travel with the work:

Problem statement.
Expected behavior.
Current behavior.
Steps to reproduce.
Acceptance criteria.
Links to designs, logs, PRs, documents, or related issues.
Screenshots and pasted images.

Descriptions support Markdown, mentions, issue-key links, pasted images, and collaborative editing.

Choose type and priority

Use Bug when something is wrong, Task for concrete work, Story for user-facing outcomes, and Epic for a larger result made of multiple issues.

Use Urgent sparingly. If everything is urgent, nothing is. Leave No priority on work that still needs triage.

Assign ownership

Set Assignee when someone owns the next action. Use Assign to me from issue surfaces when you are taking ownership yourself.

If an issue needs triage, keep it unassigned and use a triage status or label. Do not assign issues to a person just because they reported the problem.

Add labels

Use labels for routing and filtering. Create labels while creating or editing an issue when a reusable category is missing.

Good labels are short and stable. Examples:

frontend
customer-request
needs-triage
docs
blocked

Use color to make labels easier to scan, but do not rely on color alone to communicate meaning.

Set status

Move status when the work actually changes. Tixio project statuses map to categories such as Backlog, Unstarted, Started, Paused, Completed, and Cancelled.

When moving an issue into a completed or cancelled status, choose a resolution when Tixio asks for one. A resolution such as Fixed, Duplicate, Won't fix, or Obsolete helps future readers understand why the issue is done.

Add due dates and estimates

Use Due date for real date commitments. Do not use due date as a substitute for priority.

Use Estimate when the team plans with story points or relative sizing. Keep estimates current enough that cycle planning, workload, burndown, and burnup are useful.

For sprint planning, read Plan and run a sprint.

Edit an issue quickly

Most issue surfaces let you update fields inline. The issue detail page also has a quick edit path for changing multiple fields at once.

Common quick edits:

Change title.
Change status, priority, type, or assignee.
Add labels.
Set cycle, epic, milestone, due date, or estimate.
Update fix versions or affects versions.
Set custom field values when the project uses them.

If Tixio warns about unsaved changes, either save or intentionally discard the draft before leaving.

For project-specific fields, read Custom fields and Manage project custom fields.

Clone an issue

Clone an issue when a new piece of work is very similar to an existing one but should have its own status, owner, and history.

After cloning, open the new issue and adjust title, description, assignee, labels, cycle, dates, and estimates. Do not leave a clone with misleading context from the original.

Delete or cancel an issue

Deleting permanently removes an issue. Tixio recommends cancelling instead when you want to preserve comments, activity, and history.

Use delete for accidental issues with no useful history. Use a cancelled status with a resolution for real work that the team decided not to do.

A practical triage routine

For each new issue:

Confirm it belongs in the current project.
Rewrite the title if it is vague.
Add enough description for someone else to act.
Choose type and priority.
Add labels only if they help route or find the issue.
Assign an owner or leave it clearly unassigned for triage.
Set cycle, due date, estimate, epic, or milestone only when useful.