Consolidation: define priority to consolidate older tenants first
Description
PRDE - Story default text according to the team DoR (Definition of Ready)
01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
- Review the strategy we are defining to consolidate tenants, consolidating first older tenants, so we avoid accumulate many unconsolidated data.
- The goal is to always consolidate first the older tenants.
- When starting a new consolidation schedule do not add again tenants already on the queue.
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:
- Consolidate first older tenants when starting the consolidation jobs.
Activity
Show:
Details
Priority
HighAssignee
Fernando Nakamura
Reporter
MARCOS STUMPF
Labels
CAROL_BACKLOG_REVIEWPLANNED
Due Date
15 April 2024
Fix versions
CAPL_4.02
Components
BIG_QUERY | CONSOLIDATION
Created
22 February 2024, 15:53
Updated
16 April 2024, 15:16
More fields
Created: 22 February 2024, 19:53
Updated:
16 April 2024, 20:16
Github usuário pedrobuzzi realizou um commit e issue foi retornada para a coluna REVIEW no Kanban.
Esta issue foi automaticamente movimentada para QA REVIEW, pois o PR foi aprovado no Github.
Github usuário fnnakamura realizou um commit e issue foi retornada para a coluna REVIEW no Kanban.
Esta issue foi automaticamente movimentada para QA REVIEW, pois o PR foi aprovado no Github.
Esta issue foi automaticamente movimentada para REVIEW, pois o PR (não DRAFT e não WIP) foi criado no Github.
@MARCOS STUMPF ,
@Jonathan Willian Moraes , @Fernando Nakamura , @Pedro Buzzi
This issue was planned to be delivered until 2024-04-15. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-04-15, 2024-03-01, 2024-03-25
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
@MARCOS STUMPF ,
@Pedro Buzzi , @Fernando Nakamura , @Pedro Buzzi
This issue was planned to be delivered until 2024-03-25. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-03-01, 2024-03-25
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
@MARCOS STUMPF ,
@Pedro Buzzi ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-03-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-03-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.