nextcloud / nextcloud/collectives

Verification and approval process

Open
#233 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

discuss enhancement
Dominant language
JavaScript
Stars
195
Forks
51
Avg merge
1d 2h
Merged PRs (30d)
48

Description

In GitLab by @w4ts0n_ on Aug 26, 2021, 09:21

Use Case: Quality Management

In relation to the more intensive examination of knowledge management (in Nextcloud), I came across the following function request (https://help.nextcloud.com/t/task-management-workflows/10348) and would like to raise it here, as I myself also see a use case.

Person A creates a document. Person B (in brackets: if reviewing on behalf of a body: Name of the body, e.g. works council or so.) reviews this document and can approve or reject it. Person C (in brackets: if reviewing on behalf of a body: name of the body) approves or rejects the reviewed document. Only after person C approves it.

Persons B and C should perhaps also be able to provide comments, so that either person A knows (in the case of rejection by person B) what needs to be improved, or person C knows what person B has to comment on, or person B knows what needs to be looked at again more closely (in the case of rejection by person C).

In the export, a note in the form of a three-column table might be:

  1. when who created the document (person A)
  2. who checked and approved or rejected the document from person A (person B)
  3. when did who finally approve the document reviewed by person B?
  4. The version number of the document
  5. The number of revisions of the document.

It might also be useful to set deadlines (e.g. 14 days) for the second (person B) and third (person C) steps so that processes do not come to a standstill.

Notification options via e-mail and RSS feed when deadlines are exceeded.

In the case of excessive exceeding of the deadline with a reminder to the supervisor by the person who missed the deadline?

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 describes a multi-stage document review and approval workflow with comments, revisions, deadlines, exports, and notifications, but names no files, tests, or entry points. Start by reviewing how Collectives currently handles document revisions, sharing, and notifications; done would require an agreed scope and implementation covering the requested approval process.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
content
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.