Allow custom values for the "Clear time" of an user status
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
[!TIP]
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.
Feature request
Which Nextcloud Version are you currently using: 34.0.1 RC2
Is your feature request related to a problem? Please describe.
When I'm doing a break, I usually set a custom status via talk together with a "Clear after" duration. Depending on the length of the break, the values possible there are sometimes too long (like when I want something between 1 hour and 4 hours) and I choose the bigger value to ensure the message is still there, even when I'm on a break for longer then expected.
That leads to the issue, that I sometimes realize my custom status is still set, although I'm already back from my break for over an hour.
Describe the solution you'd like
It would be great to input a custom duration for a user status (like 90 minutes). If it's additionally possible to set a specific time to expire (like 3:15pm), it would save my mind from some time-span calculations as well. 😄
Describe alternatives you've considered
Probably should get myself into resetting it manually whenever I come back... But sometimes the first messages are being read after returning to desk and I simply forget to do that.
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
Start by locating the Nextcloud Talk user-status controls and the existing "Clear after" duration options. Read how status expiry is represented and handled, then determine whether custom durations and a specific expiration time fit the current flow. Done means users can set either requested form of custom expiry and the status clears at the selected time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100