RocketChat / RocketChat/Rocket.Chat

UX: Idle Time Limit misses unit

Open
#33,566 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

planned
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

In the account preferences, there's an option to enable the "Auto Away" feature and an option to define an "Idle Time Limit". The text box provides no guidance about what unit this time limit is defined in. Based on the number (3600 in my case), a more technical user can probably deduct that the unit is seconds, but it would be helpful to provide some guidance here, at least by informing the user that the limit is defined in seconds, ideally by giving them a way to define the value in a more human-readable way (in hours, minutes, seconds).

Screenshot 2024-09-27 at 09 51 44

Steps to reproduce:
  1. Click your avatar icon
  2. Select "Preferences"
  3. Select "User Presence"
  4. Note the input field for "Idle Time Limit" showing a number without any units associated
Expected behavior:

The Idle Time Limit input field should indicate the unit used, or provide a more human-friendly way of selecting a time period.

Actual behavior:

The input fields does not provide any guidance of what to enter here.

Server Setup Information:

N/A (can't provide this information as a regular user on our platform)

Client Setup Information
  • Desktop App v4.1.1 on macOS

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 in the account Preferences flow at User Presence and inspect the Idle Time Limit input described in the reproduction steps. Confirm how the current value is entered, then make the unit clear or provide a human-readable time-period control; verify the result in the same flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.