Organization: Tenant list flickering
Description
CAPL - Bug default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
@Breno Zipoli Monteiro Papa
@Andre Pasold
02 - PROBLEM (WHAT'S THE ISSUE?):
- Some clients are reporting this "shaking" or "blinking" behaviour in the tenant administration page on organization's main page. This does not block any actions on user side. The video was recorded in https://totvstechfindev.carol.ai/carol-org/admin/tenants and using 1920x1080 resolution. The user says that this always happens for the last 2 months and
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):- Access CArol as Organization Admin
- Chec tenant list
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):
Activity
Show:
Details
Priority
HighAssignee
Carlos Affonso Wagner
Reporter
Douglas Coimbra Lopes
Labels
PLANNEDPROD_IMPACT
Due Date
1 January 2024
Fix versions
CAPL_3.97
Components
ORGANIZATION_ADMIN | TENANTS
Created
16 November 2023, 10:41
Updated
4 January 2024, 22:18
More fields
Created: 16 November 2023, 14:41
Updated:
5 January 2024, 02:18
This issue was automatically transitioned to DONE after being deployed to production on Github.
https://github.com/totvslabs/carol-ui/releases/tag/v4.39.0
No associated issue on JIRA TOTVS BRAZIL.
@Douglas Coimbra Lopes ,
@Pedro Buzzi , @Carlos Affonso Wagner , @Andre Pasold , @Douglas Coimbra Lopes , @Moises Jose Soares Filho
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.
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master 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 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).
fix(tenant list):
CAPL-5026 Done tenant list flickering
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.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
fix(tenant list):
CAPL-5026 Done tenant list flickering
@Douglas Coimbra Lopes ,
@Geny Isam Hamud Herrera , @Carlos Affonso 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.