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

Automation for Jira 3 April 2024, 16:59 Jira Internal Users

Github usuário pedrobuzzi realizou um commit e issue foi retornada para a coluna REVIEW no Kanban.

Automation for Jira 3 April 2024, 16:59 Jira Internal Users

Esta issue foi automaticamente movimentada para QA REVIEW, pois o PR foi aprovado no Github.

Automation for Jira 1 April 2024, 15:46 Jira Internal Users

Github usuário fnnakamura realizou um commit e issue foi retornada para a coluna REVIEW no Kanban.

Automation for Jira 1 April 2024, 15:35 Jira Internal Users

Esta issue foi automaticamente movimentada para QA REVIEW, pois o PR foi aprovado no Github.

Automation for Jira 27 March 2024, 14:31 Jira Internal Users

Esta issue foi automaticamente movimentada para REVIEW, pois o PR (não DRAFT e não WIP) foi criado no Github.

https://totvslabs.atlassian.net/browse/CAPL-5557#icft=CAPL-5557 Consolidation define priority to consolidate older tenants first

Automation for Jira 25 March 2024, 20:31 Jira Internal Users

@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.

Automation for Jira 13 March 2024, 14:38 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

https://totvslabs.atlassian.net/browse/CAPL-5557#icft=CAPL-5557 Consolidation define priority to consolidate older tenants first

Automation for Jira 1 March 2024, 20:01 Jira Internal Users

@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.

Automation for Jira 26 February 2024, 14:48 Jira Internal Users

@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.