Staging area deve mostrar atributos de stagingMapping ao invés de schemaMapping

Description

PRDE - Bug default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM): <text>
02 - PROBLEM (WHAT'S THE ISSUE?):

Avaliando os atributos de cada atributo interno: stagingMapping e schemaMapping:

Na staging esta mostrando mais atributos que temos internamente, isso porque está mostrando baseado no “schemaMapping”.

E no bigquery mostra baseado em “stagingMapping“:

05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):

  • UI da staging area deve mostrar colunas provenientes de stagingMapping.

Activity

Automation for Jira 3 April 2024, 13:44 Jira Internal Users

Esta issue foi automaticamente movida para WAITING DEPLOY, pois a issue relacionada de QA regression também chegou ao status WAITING DEPLOY (PR foi mergeado na branch master no Github).

Automation for Jira 2 April 2024, 12:38 Jira Internal Users

Esta issue foi automaticamente movida para REGRESSION, pois o PR foi mergeado na branch QA no Github.

Automation for Jira 2 April 2024, 12:38 Jira Internal Users

Esta issue foi automaticamente movida para REGRESSION, pois o PR foi mergeado na branch QA no Github.

Automation for Jira 2 April 2024, 12:38 Jira Internal Users

Esta issue foi automaticamente movida para REGRESSION, pois o PR foi mergeado na branch QA no Github.

Automation for Jira 2 April 2024, 12:38 Jira Internal Users

Esta issue foi automaticamente movida para REGRESSION, pois o PR foi mergeado na branch QA no Github.

Automation for Jira 2 April 2024, 12:38 Jira Internal Users

Esta issue foi automaticamente movida para REGRESSION, pois o PR foi mergeado na branch QA no Github.

Automation for Jira 2 April 2024, 11:28 Jira Internal Users

Esta issue foi automaticamente movida para TESTED & MERGED, pois o PR foi mergeado na branch Develop no Github. PR aprovado por felabs01,douglascoimbra.

Automation for Jira 1 April 2024, 19:45 Jira Internal Users

Github usuário douglascoimbra aprovou um PR e foi adicionado como Shared Assignee nesta issue.

chore(ST): https://totvsiddia.atlassian.net/browse/CAPL-5630#icft=CAPL-5630 build fields list based on `mdmStagingMapping`

Automation for Jira 28 March 2024, 15:44 Jira Internal Users

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

Automation for Jira 25 March 2024, 19:30 Jira Internal Users

@Robson Thanael Poffo ,
@Jonathan Willian Moraes , @Carlos Affonso Wagner ,

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-25

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Automation for Jira 22 March 2024, 23:14 Jira Internal Users

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

chore(ST): https://totvslabs.atlassian.net/browse/CAPL-5630#icft=CAPL-5630 build fields list based on `mdmStagingMapping`

Pedro Buzzi 21 March 2024, 13:59 Jira Internal Users

Detalhes de implementação foram discutidos em: https://totvscarol.slack.com/archives/C03LA7B048G/p1710939185101539

Automation for Jira 15 March 2024, 13:30 Jira Internal Users

@Robson Thanael Poffo ,
@Carlos Affonso Wagner ,

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-25

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.