Carol Admin: list and manage users
Description
DAEN - Story default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
On Caro Admin Flow, I should be able to visualize, add and remove Carol Admin roles.
- Allow to remove the carolAdmin whole for an user.
- Allow to add a new user as carolAdmin
- List all users with the whole Carol Admin.
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:
- Required: Insert Users tab into Carol Admin management
- List all users with the role Carol Admin
- Required: Change “Add Organization” button position to the Organization Management tab, on table header, instead of the page header
- Optional (we can implement this later): Allow to add/edit an user:
- Allow to remove the carolAdmin whole for an user.
- Allow to add a new user as carolAdmin
Activity
Show:
Details
Priority
HighAssignee
Ingo Wagner
Reporter
Robson Thanael Poffo
Labels
CAROL_BACKLOG_REVIEWPLANNED
Due Date
1 January 2024
Fix versions
CAPL_3.97
Components
ORGANIZATION_ADMIN | USERSTENANT_ADMIN | USERS
Created
8 November 2023, 23:51
Updated
15 January 2024, 11:19
More fields
Created: 9 November 2023, 03:51
Updated:
15 January 2024, 15:19
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp,moisesjsf.
Github user moisesjsf has just approved a PR (added as Shard Assignee in this Jira issue).
feat(carol-admin): https://totvslabs.atlassian.net/browse/CAPL-4992#icft=CAPL-4992 list admins
This card has been validated by the QA team.
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
@Andre Pasold @Jonathan Willian Moraes Due to the prioritization of this release, we will test this card in production since we don’t have the carol admin token for sandboxes
cc @Ingo Wagner
@Moises Jose Soares Filho @Andre Pasold @Jonathan Willian Moraes the tests are blocked due to the reported item: https://totvscarol.slack.com/archives/C029SLMQ092/p1702562044503339
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
feat(carol-admin): https://totvslabs.atlassian.net/browse/CAPL-4992#icft=CAPL-4992 list admins
@Robson Thanael Poffo ,
@Pedro Buzzi , @Ingo Wagner ,
This issue was planned to be delivered until 2024-01-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-12-11, 2024-01-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
@Ingo Wagner It was suggested that every time a new CarolAdmin is created, we send a Slack notification. Please evaluate if that is a something smooth to have, otherwise we can create a new card for that particular demand.
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Ingo Wagner ,
This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-12-11
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.