nextcloud / nextcloud/tables

Append to cell

Open
#2,035 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Is your feature request related to a problem? Please describe.

Problem identified : Not possible on the same cell to append content. All content is available.

Issue I would like to solve : only one row for multiple users, instead of multiply the same row for multiple users.

We are working in a regulatory environment where we do track the readings of our documents by individual users. We usually have to sign the entry in a table to show that we did read the document on the date xxx.

I believe the Tables app could replace already that today with creating for each user an indiviual row of what they need to read, but this solution will require 100s of raws, while one raw could be sufficient with the proposed solution.

Describe the solution you'd like

.Have a column with all the users that must read the document XX
.Have a column with all the users that have read the document XX <= Append to cell userid to this column automatically filled in.
.Have a column which can append some data to the same cell (Tick box (I have read the following document )and . Date)

Create a filter view with userid that needs to read the document and have not read the document = People can track who has not read the document.

Describe alternatives you've considered

Like as said, one row for each user, but this seems unmanageable by someone with lots of users. Would need some automation...and the table app would be quickly filled in.
The solution above seems manageable by a human with groups and circles, and would reduce the size of the table drastically.

Additional context

Very good for small teams etc...

Note: the appended row will be added to a rich text field table.

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

No files, tests, or entry points are named. Start by reviewing the Tables app's existing cell, rich-text, user, and filter-view behavior, then clarify how append operations, read tracking, permissions, and dates should work. Done should support the proposed user lists, automatic appending, and filtering users who have not read a document.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.