Skip to main content

Work and bug tracking

Gitea Issues holds the implementation backlog: features, defects, research, documentation, and release work. Issues connect the problem and acceptance criteria to an owner, discussion, dependencies, pull requests, and verification.

Making work visible​

A useful issue explains the problem, the intended outcome, included scope, acceptance criteria, and how the result will be checked. Its assignee owns the next action. Dependencies identify work that must finish first; labels and milestones help organise priorities and delivery periods.

The agreed board flow is Backlog → In Progress → Review & Test → Done. Priority and area labels help filter the backlog without replacing the issue's description. The detailed issue and PR record explains progress when a board column alone would be ambiguous.

Issue #10 records the process and board setup. Later governance snapshots identified missing dependency and board evidence, so the planned flow should not be read as confirmation that every item used it consistently. Current assignment and state come from the tracker, rather than a historical issue plan.

Issues and pull requests​

Implementation starts on a short-lived branch. The issue records the branch, progress, discoveries, and blockers; a linked PR explains the resulting change and its checks. Review findings return to the branch for correction. The methodology describes the review and CI gates without repeating their configuration here.

Use a closing link when the PR satisfies the whole issue. Partial work should use a related-work link and leave unmet acceptance criteria visible. After merge, reconcile the issue, board, follow-up defects, and remaining release checks. A closed issue cannot stand in for an unrecorded manual test or retest.

Bug reports​

A bug is implemented behaviour that differs from an agreed requirement. A usability finding records difficulty using the product; it may require more investigation before it becomes a confirmed defect. A feature adds capability. This distinction helps the team prioritise evidence and avoid treating every suggestion as a requirement.

A reproducible bug report includes:

  • expected and observed behaviour;
  • steps, application state, and relevant device or browser details;
  • impact and a proportionate priority;
  • sanitised evidence, such as a screenshot or request ID; and
  • the correction's acceptance criteria and regression check.

Gitea's bug label identifies defect work. Sprint 3 governance also allows reports originating in YouTrack to link to a Gitea implementation issue and PR. When two tools are involved, cross-links keep the report, fix, and retest aligned. The project methodology describes that relationship; it does not establish an audited YouTrack inventory.

Workflow in practice​

Issue #9 defined the API foundation work. Its linked PR #28 shows how that task moved through implementation, peer review, correction, and merge. Select an image to open the full-size screenshot.

1. Define and assign the work​

Issue #9 sets out the purpose, included and excluded scope, and acceptance criteria. Tyron owns the work, with labels and the Sprint 1 milestone providing planning context.

2. Implement and record checks​

PR #28 summarises the branch's changes and records local automated and manual checks. The “Repository CI passes” item is unchecked; this screenshot does not establish a complete CI pass.

3. Review and request a correction​

Uzair identifies a vulnerable dependency during independent review and requests an update before approval. The review records both the finding and the checks performed.

4. Correct, recheck, and merge​

Tyron records the dependency update and repeat checks. Uzair rechecks the latest commit, records successful local checks, approves the change, and merges it into main. The completed branch is then deleted.

AI declaration: Prepared and edited with assistance from Codex[GPT-5], Codex-CLI[GPT-6], and Codex[GPT-6]. The latest revision used Codex[GPT-6] for rubric comparison, source review, prose editing, and screenshot layout and captions.