openimsdk / openimsdk/openim-docker
[BUG] OpenIM admin backend has a bug when adding notification accounts.
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 88
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Description
OpenIM Server Version
openim/openim-admin-front release-v1.8.4
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Docker Deployment
Bug Description and Steps to Reproduce
Function Module:
OpenIM Admin Backend - IM System - Notification Management - Notification Account - Add New
When adding a notification account, the system prompts a parameter error indicating that the appMangerLevel parameter is missing.
Figure 1 is a screenshot reproducing the bug, and Figure 2 is a screenshot of successfully adding the account after including the appMangerLevel parameter via a Postman simulation.
Screenshots Link
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 with the OpenIM Admin Backend notification account add flow under IM System > Notification Management > Notification Account, and compare its request with the successful Postman reproduction. Done means a new notification account can be added without the missing appMangerLevel parameter error in the Docker deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100