Problem Statement
Kaneo tickets have no way to link back to the code that implements them. There are two gaps:
- Resources are read-only. If an external gitea issue is synced, a nice linked entry appears there. But there is no way to manually add a resource — no button, no form, no input. You cannot link a commit, a PR, a GitHub/GitLab issue, a Gerrit change, or even a design doc URL.
- No commit-to-ticket traceability. When a ticket is resolved, there is no standard field or mechanism to record which commit implemented it. Jira solves this with custom labels (e.g., "Tech solution") and by letting you link any external issue, commit, or PR to a ticket.
The practical result: after landing a fix, you have no way in kaneo to navigate from the ticket to the code change. For self-hosted setups using GitLab, Gerrit, or plain git, the trace is completely lost.
Proposed Solution
Manual resource management on tickets:
- Add an "Add resource" button/action in the Resources section of a ticket.
- Allow pasting a URL with an optional label (e.g., fix: prevent overflow → commit a1b2c3d).
- Auto-detect known URL patterns (GitHub/GitLab/Gitea commit, PR, issue; Gerrit change-id) and display a contextual icon/label.
- Manually added resources appear alongside synced ones with the same visual treatment.
Alternative Solutions
- Put everything in the ticket description as a raw link. Works today but is unstructured, invisible to search, and doesn't integrate with the Resources panel.
- Use a custom field. If kaneo had custom fields, a "Commit" URL field could serve this purpose, but it would lack the visual polish and discoverability of a native Resources entry.
- Auto-detect ticket IDs in commit messages via webhook. More automation but more implementation surface; manual linking solves 80% of the pain without backend complexity.
Relevant Context
Does this feature align with Kaneo's focus on simplicity?
Yes. The Resources UI already exists. An "Add resource" button and an optional "Resolved by" field add minimal surface. No new data model is needed (resources are likely already a table). No new settings or configuration screens. It makes the existing Resources feature more useful for teams not on gitea while changing nothing for current gitea users.
Problem Statement
Kaneo tickets have no way to link back to the code that implements them. There are two gaps:
The practical result: after landing a fix, you have no way in kaneo to navigate from the ticket to the code change. For self-hosted setups using GitLab, Gerrit, or plain git, the trace is completely lost.
Proposed Solution
Manual resource management on tickets:
Alternative Solutions
Relevant Context
Does this feature align with Kaneo's focus on simplicity?
Yes. The Resources UI already exists. An "Add resource" button and an optional "Resolved by" field add minimal surface. No new data model is needed (resources are likely already a table). No new settings or configuration screens. It makes the existing Resources feature more useful for teams not on gitea while changing nothing for current gitea users.