Bug #2218
open
Notifications : Same notification count will appear for all accounts but it should display according to groups .
Added by Vengadeshwaran R about 1 year ago.
Updated 1 day ago.
Description
Steps:
1. Log in to Lauditor.
2. Click on Notifications located on the left side.
3. Review the notifications:
- The same notification count will appear across all accounts.
For specific roles:
Admin: Only notifications related to meetings should be displayed.
Group Head/Team Member: Notifications should be displayed based on groups, including Relationship, Documents, and Meetings.
Super User: All related notifications should be displayed.
Files
|
1.mov (2.74 MB)
1.mov |
|
Vengadeshwaran R, 01/22/2024 05:46 AM
|
|
- Description updated (diff)
- Assignee set to muskan mathur
- Description updated (diff)
- Status changed from New to Resolved
- Assignee changed from muskan mathur to Vengadeshwaran R
- Status changed from Resolved to New
- Assignee changed from Vengadeshwaran R to muskan mathur
- Status changed from New to Resolved
- Assignee changed from muskan mathur to Vengadeshwaran R
- Status changed from Resolved to New
- Assignee changed from Vengadeshwaran R to muskan mathur
- Status changed from New to Resolved
- Assignee changed from muskan mathur to Vengadeshwaran R
- Status changed from Resolved to New
- Assignee changed from Vengadeshwaran R to muskan mathur
1.The request is sent from Lauditor to Vitagist or other products. If they accept our request, we will receive a notification for the SU and the respective group team members.
2.The request is sent from other products to Lauditor and we will receive a notification for the Super User accounts.
3.The document is shared from Vitagist to Lauditor, and we will receive a notification for the Super User and the respective group team members.
Link - https://drive.google.com/file/d/1wfLIsBoFV0PURfcPUDmQQxdFF7GxMwS2/view?usp=drive_link
- Status changed from New to Resolved
- Assignee changed from muskan mathur to Vengadeshwaran R
This issue can only be checked once bug no. 4179 is fixed.
Also available in: Atom
PDF