Working together
Issues, labels & boards
An issue is a note about work: a bug, a feature idea, a question. Each issue has a number (#12) you can reference anywhere.
Creating an issue
Issues tab β New issue. Write a clear title and a Markdown description β the Preview tab shows the result. Anyone signed in who can see the repo may create issues.
Mark it Confidential for sensitive matters (e.g. a security hole): only reporters and above, the author, and assignees can see it. Confidential issues are never sent to Rembug or webhooks.
Organizing issues
In the issue sidebar (Reporter role and above):
- Assignees β who works on it. If an assignee uses Kala, the issue automatically becomes a task in their Kala (list Lumbung). Completing the task in Kala closes the issue and vice versa; due dates stay in sync.
- Labels β categories such as
bug,feature. Manage them in Issues β Labels. - Milestone β a release target with due date & progress.
- Due date β overdue issues are highlighted in red.
Referencing & auto-closing
In issues, MRs, comments, and commit messages:
| Write | Result |
|---|---|
#12 |
link to issue 12 |
!7 |
link to merge request 7 |
@name |
mention someone (notified if they can see it) |
Closes #12, Fixes #12, Resolves #12 |
issue 12 closes when the commit/MR reaches the main branch |
Board
The Board tab shows issues as cards in columns: Open, one column per label, and Closed. Drag cards between columns to change labels or close issues. On phones/tablets use the Move to⦠menu on a card.
Discussing in Rembug
When the repo is linked to a Rembug channel (Settings β Rembug channel), every issue opens a topic there and its comments flow in β the team can discuss from Rembug without opening Lumbung.