DM field reordering: unexpected behaviour when moving nested fields
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):
02 - PROBLEM (WHAT'S THE ISSUE?):
When you change the position of a nested field, the children are left behind, as if they were children of the new field in that position. After saving, it displays correctly once again.
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
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
LowAssignee
Carlos Affonso Wagner
Reporter
Carlos Affonso Wagner
Labels
PLANNED
Due Date
12 February 2024
Fix versions
CAPL_3.99
Components
DATA_MODEL | VIEW
Created
29 November 2023, 09:56
Updated
12 February 2024, 13:11
More fields
Created: 29 November 2023, 13:56
Updated:
12 February 2024, 17:11
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 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.
@Carlos Affonso Wagner ,
@Jonathan Willian Moraes , @Chámam Diomede Caires , @Ingo Wagner
This issue was planned to be delivered until 2024-02-12. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-23, 2024-02-12, 2024-01-02
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by felabs01.
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(DM): reordering nested fields
@Carlos Affonso Wagner ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-01-22. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-22, 2024-01-02
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
@Carlos Affonso Wagner ,
@Pedro Buzzi ,
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: 2024-01-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.