nextcloud / nextcloud/deck

Indicate card creator on top of card, beside the creation date (for better collaboration)

Open
#6,891 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop design enhancement skill: frontend ux
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

Problem description :

It happens regularly at work, during meetings, that we wonder who created a card we've never seen before (a card created between two meetings).

One solution is to look in the activities tab to see who created it.
This is only possible if the information is still available. After a long existence, the information can no longer be found, or, if it still exists, a fairly long history needs to be unrolled. In other words, this way, it's either impossible or not practical or intuitive.

I therefore propose to display this information directly after the creation date, below the title. This way, you'll know right away who created the card, and therefore who to contact for more information on the "UFO" card.

What we currently have :

Image

What I suggest :

Image

Bonus :

It would be great to indicate also (same way) who last modified the card : "Modified: 12 days ago by John Doe"
This avoids having to look in the activities for the last action performed, especially if it were to disappear after a while.

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 locating the card header rendering and the existing creation-date or activity data, then determine whether the creator is available there. Done means the creator is shown beside the creation date, with the last modifier included only if that data is available and the bonus is in scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.