Issues

Issues provide a repository-level record for bugs, requests, and planned work. They support labels, assignees, comments, reactions, a change timeline, and open or closed state.

Find work to triage

The dashboard supports searching, filtering, and sorting issue lists. From the CLI, fetch a sufficiently large page before concluding that no issue matches a local filter:

try issue list -R OWNER/NAME --state open --per-page 100
try issue view NUMBER -R OWNER/NAME
try issue timeline NUMBER -R OWNER/NAME

The issue view shows the current description and metadata. The timeline adds the sequence of comments and state or assignment changes needed to understand how the issue reached its current state.

Create and edit

Use a body file for a report with reproduction steps or other multiline detail:

try issue create -R OWNER/NAME \
  --title "Concise issue title" \
  --body-file issue-body.md

After creation, the title, description, labels, and assignees can be updated. Comments carry follow-up discussion, and reactions provide a lightweight way to acknowledge an issue or comment without adding another message.

try issue comment NUMBER -R OWNER/NAME \
  --body-file comment.md

Manage labels and assignees

Labels classify work independently of assignees. Add and remove labels when you need to preserve every unrelated label already on the issue:

try issue label NUMBER -R OWNER/NAME \
  --add triage \
  --remove needs-info

Assignees identify the people currently responsible for the next action. Keep labels descriptive and use assignees for ownership so filtering remains useful as the issue changes state.

Close and reopen

Close an issue when the work is complete or no longer planned. Reopen it when new evidence or follow-up work makes the issue active again:

try issue close NUMBER -R OWNER/NAME
try issue reopen NUMBER -R OWNER/NAME

Read the issue again after changing state so comments and automation that raced with the action are not overlooked.

Enable or disable issues

Repository administrators can enable or disable the issue tracker in repository settings. Disable it only when the team has another durable tracking system; pull request discussion remains separate from repository issues. Projects are not currently available as a replacement inside Trylle.

See repositories for the other repository settings and pull requests for reviewing the changes that implement an issue.