nextcloud / nextcloud/deck

Enhancements of activity timeline

Open
#3,584 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
The root of the problem is, that open cards do not refresh automatically, so when I have an open card and a colleague edits it and then I modify it later, the changes of my colleague are overwritten (maybe that's an issue on it's own).

It would be more easy to restore his information using the timeline tab if one would have the possibility to restore and/or copy the card at that time.
This is currently difficult, because:

  • In "bigger view" one cannot copy the text at all -> has been solved
  • Long Descriptions are cut at some point
  • Line breaks are not stored

Describe the solution you'd like

  • It would be nice to have a restore and/or copy button to go back to a certain state or merge the changes externally
  • The copy button should paste the complete text to the clipboard
  • Line breaks should be stored
  • Furthermore it would enhance the usability if the text in the timeline when in "bigger view" behaves as the one in sidebar view (can be marked/copied) -> has been solved

Describe alternatives you've considered
Reading the information from the database is quite cumbersome and still the missing line breaks are a problem.

Additional context
Nothing to add.

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

Start with the activity timeline tab, comparing the bigger view with the sidebar view and checking how long descriptions and line breaks are displayed. Define whether restore or copy is in scope, then verify that copying preserves complete text and that line breaks remain intact; the restore or merge behavior needs a clear decision before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.