nextcloud / nextcloud/deck

Add board timeline + per-card change log (who changed what and when) in Deck

Open
#7,451 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

Environment:

  • Nextcloud: 32.0.1
  • Deck: 1.16.2
  • Client: Web UI (browser: brave
  • DB: MySQL
  • Install type: manual

Problem:
We use Deck with multiple users. Cards can be edited by several employees, but there is no reliable audit trail that shows who changed what and when. We need both:

  1. a board-level timeline (overview of events)
  2. a per-card change history (detailed)

Feature request / Expected behaviour:

A) Board timeline (overview)
Show a chronological timeline for the board including:

  • card created / archived / restored / deleted
  • card moved between stacks (from -> to)
  • assignee changes
  • due date changes
  • label changes
  • attachments added/removed
  • comments added/edited (if supported)

B) Per-card change log (detail)
Inside each card, add an “Activity / History” view that records at least:

  • title changes (old -> new)
  • description changes
  • checklist item add/edit/complete/uncomplete/delete
  • due date changes
  • assignees changes
  • label changes
  • attachments added/removed
  • card moved (stack/position)
  • archive/restore

Requirements:

  • Show: user + timestamp + action + field (and previous/new value where meaningful)
  • Ideally filter/search + export (JSON/CSV)
  • Privacy: do not log full description text by default (log “description changed”; optional diff or previous value only behind a permission/setting)

Why:
Accountability, coordination in teams, and compliance/audit requirements.

Related issues:

  • #1281 (History/timeline for a board)
  • #1558 (Timeline and activity)
  • #7201 (Visual diff-style output for card description changes)
  • #7058 (Activity log with card description / avoid full text logging)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by reviewing related issues #1281, #1558, #7201, and #7058 to understand existing discussion; done requires an agreed scope for board and card history, privacy behavior, and any filtering or export requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, mysql
Domain
backend-api-design, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.