Allow to restrict the Message of user status for more privacy
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: dav
feature: status
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
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.
Summary
- Employees might be forced to set an OOO messages and user status by policy
- Guest account users on the instance can also see their OOO messages and user status
- It would be good to be able to limit the visibility of both while keeping the general information still available (OOO: duration, replacement, the-fact-its-happening, status: DND/Away/Online)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; begin by tracing how user status and out-of-office messages are currently exposed to guest accounts. Done means visibility can be restricted while general status information and OOO duration, replacement, and occurrence remain available as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100