Bug Triage Board for Nextcloud Deck
as a normal Nextcloud Deck board.
Download the JSON, preview the stacks/cards, or use Deckloud's template flow when it is available. The created result is a regular board on your own Nextcloud server.
Board preview
Bug Triage
Reported
Reproduced
Prioritized
Fixing
Verify
Closed
JSON
Portable v1 template schema
{
"schema": "deckloud-template-v1",
"schemaVersion": 1,
"slug": "bug-triage-nextcloud-deck",
"locale": "en",
"title": "Bug Triage Board for Nextcloud Deck",
"description": "A practical board for incoming bug reports, reproduction, priority decisions, fixing, verification, and closure.",
"category": "software",
"tags": [
"bugs",
"support",
"triage"
],
"quickCreateStackKey": "reported",
"compatibility": {
"requiresBoardCreate": true,
"includesAttachments": false,
"includesComments": false
},
"board": {
"title": "Bug Triage",
"color": "EF4444"
},
"labels": [
{
"key": "bug",
"title": "Bug",
"color": "EF4444"
},
{
"key": "regression",
"title": "Regression",
"color": "B91C1C"
},
{
"key": "needs-info",
"title": "Needs Info",
"color": "F59E0B"
},
{
"key": "enhancement",
"title": "Enhancement",
"color": "3B82F6"
}
],
"stacks": [
{
"key": "reported",
"title": "Reported",
"order": 1
},
{
"key": "reproduced",
"title": "Reproduced",
"order": 2
},
{
"key": "prioritized",
"title": "Prioritized",
"order": 3
},
{
"key": "fixing",
"title": "Fixing",
"order": 4
},
{
"key": "verify",
"title": "Verify",
"order": 5
},
{
"key": "closed",
"title": "Closed",
"order": 6
}
],
"cards": [
{
"stack": "reported",
"title": "Add report template to description",
"description": "Expected, actual, server version, Deck app version, client version, logs, repro steps.",
"labels": [
"needs-info"
]
},
{
"stack": "reproduced",
"title": "Confirm repro on clean account",
"description": "Use a clean board before deciding if this is user data, upstream, or app behavior.",
"labels": [
"bug"
]
}
]
}01
What this creates
6 stacks, 4 board labels, and 2 starter cards. Attachments and comments are intentionally omitted so the template stays portable.
02
Why it fits Deckloud
The template is just a recipe for standard Deck objects. No hosted workflow account, no relay backend, and no Deckloud-only object model.
03
Safe import rules
IDs are not stored. Stack and label keys are remapped at creation time, and due dates use relative offsets instead of stale fixed dates.
FAQ
Practical questions
Does this change my Nextcloud server schema?
Does the template include comments or attachments?
Can I edit the board after creating it?
Related
Nextcloud Deck templates, made for real boards.
Download practical Nextcloud Deck templates for kanban, GTD review, releases, bug triage, content calendars, meetings, offline work, and SEO sprints.
OpenBuild a Nextcloud Deck template without sending server data anywhere.
Build a simple Deckloud template JSON in your browser for a Nextcloud Deck board. No account, no upload, no server credentials.
OpenCreate templates that stay portable.
Create portable Nextcloud Deck board templates with stack keys, label keys, starter cards, and relative due dates.
Open