nextcloud / nextcloud/files_lock

enh: allow file owner to unlock TYPE_TOKEN locks not working in Team Folders

Open
#1,181 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
JavaScript
Stars
39
Forks
10
Avg merge
1d 11h
Merged PRs (30d)
48

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • 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.

Feature request

Which Nextcloud Version are you currently using: (see administration page)
Nextcloud Hub 25 Autumn](https://hetzner.com/) (32.0.9)

Is your feature request related to a problem? Please describe.
File owner cannot force unlock from another user lock if file is in Team Folders

Describe the solution you'd like
File owner should be able to force unlock from another user lock if file is in Team Folders, like in regular shared folder

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

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 locating TYPE_TOKEN lock handling in the files_lock repository and comparing Team Folders with regular shared folders. Done means the file owner can force-unlock another user's lock in a Team Folder, matching the behavior requested for regular shared folders.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.