nextcloud / nextcloud/approval

Approvals are not visible in External Storage

Open
#373 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
39
Forks
10
Avg merge
20m
Merged PRs (30d)
4

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.

Steps to reproduce
  1. Install External Storage
  2. Connect external Storage via WebDav
  3. Setup approval process
  4. Request approval of a file located on External Storage
  5. Check file status in External Storage
Expected behaviour

Tell us what should happen

Approval Status and assigned Tag are visible to everybody who has access to External Storage.

Actual behaviour

Tell us what happens instead, if possible also add a screenshot

Approval Status and assigned Tag are NOT visible to everybody who has access to External Storage. It is visible only to the requester and approver. I think it is due to the internal share created by the app. External Storage must be shared via Nextcloud so users can see approvals.

Server configuration

Web server: Apache/Nginx

Database: MySQL/Maria/SQLite/PostgreSQL

PHP version: 8.2/8.3/8.4

Nextcloud version: (see Nextcloud admin page)

[Nextcloud Hub 10] (31.0.10)

List of activated apps
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Nextcloud configuration
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Browser

Browser name: Firefox/Chrome/Safari/…

Browser version: 124/125/…

Operating system: Windows/Ubuntu/Mac/…

Windows

Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...

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 by reproducing the issue through the listed WebDAV External Storage and approval-process steps, then trace how approval status and assigned tags are exposed for externally stored files. Done means users with access to the External Storage can see both the approval status and assigned tag, not only the requester and approver.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.