RocketChat / RocketChat/Rocket.Chat
Omnichannel - offline Mail not forwarded to Department Mail-Address
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
We have several departments in Omnichannel/Live Chat, with different mail addresses to which messages should be sent when Live Chat is offline. Unfortunately, this does not work. The emails all go to the mail address that is set in Settings > Omnichannel > Live Chat.
Unfortunately, the mail address set in Omnichannel > Departments > Edit > Mail address is not considered at all and no offline messages are sent there.
Steps to reproduce:
- Omnichannel
- Departements
- Edit
- Give Mail-Address
- Try offline Live-Chat
Expected behavior:
The offline Message should be send to the Mail-Address which is set for the departementActual behavior:
It send the offline message to the mail-address, which is set under general settings for the omnichannel.Server Setup Information:
- Version of Rocket.Chat Server: 6.2.8
- Operating System: Ubuntu 22.04
- Number of Running Instances: 1
- NodeJS Version: 14.21.3
- MongoDB Version: 5.0.18
Client Setup Information
- Desktop App or Browser Version: Webbrowser Firefox 115.0.2
- Operating System: Windows 11
Additional context
Relevant logs:
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 reproducing the offline Live Chat flow with a department mail address configured under Omnichannel > Departments, then trace how the destination address is selected. Done means an offline message for a department is delivered to that department's configured address rather than the general Omnichannel address.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100