RocketChat / RocketChat/Rocket.Chat

Omnichannel --> Agents --> Edit --> Departments - not user-friendly

Open
#24,072 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:

Omnichannel --> Agents --> Edit --> Departments is actually not user friendly, when the agent is set to many departments (like 4 or more).

Steps to reproduce:
  1. Go to Omnichannel.
  2. Click on Agents.
  3. Click on Edit.
  4. Departments, select many departments.
Expected behavior:

Adding and Deleting departments happens in an user-friendly interface.

Actual behavior:

I've added screenshots to show why we think it's not user-friendly. It's difficult to read which departments are already added, to add more departments and we could also delete departments by accident.

Server Setup Information:
  • Version of Rocket.Chat Server: 4.3.0
  • Operating System: Ubuntu
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: yes
  • NodeJS Version: v12.22.8
  • MongoDB Version: 4.0.13
Client Setup Information
  • Desktop App or Browser Version: Chrome
  • Operating System: Windows
Additional context

Screenshots:

image

image

image

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 Omnichannel → Agents → Edit → Departments with many departments, using the attached screenshots as the reference. Done means the selected departments are easy to read, additional departments can be added, and departments cannot be deleted accidentally.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.