-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI Does Not Reflect Saved Default Action in Content Types Update Dialog #29765
Labels
Comments
valentinogiardino
moved this from Gardening Day Backlog
to QA - In Progress
in dotCMS - Product Planning
Sep 6, 2024
valentinogiardino
moved this from QA - In Progress
to In Progress
in dotCMS - Product Planning
Sep 6, 2024
3 tasks
3 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 10, 2024
### Proposed Changes * Emit the initial value of the form in `workflowsSelected$` observable. * Add a check to ensure the workflow actions dropdown exists before attempting to clear it. ### Checklist - [x] Tests - [x] Translations - [x] Security Implications Contemplated (add notes if applicable) ### Additional Info This PR fixes: 1. #29765 2. #29762 ### Screenshots #### Before ![image](https://github.com/user-attachments/assets/f9851368-7479-4a9c-a354-77c82093a0c9) #### After https://github.com/user-attachments/assets/766cb82a-763f-4d57-8325-14eaba622455
github-project-automation
bot
moved this from In Review
to Internal QA
in dotCMS - Product Planning
Sep 10, 2024
github-project-automation
bot
moved this from Internal QA
to Current Sprint Backlog
in dotCMS - Product Planning
Sep 10, 2024
valentinogiardino
moved this from Current Sprint Backlog
to Internal QA
in dotCMS - Product Planning
Sep 10, 2024
Looks good to me |
fabrizzio-dotCMS
moved this from Internal QA
to QA - Backlog
in dotCMS - Product Planning
Sep 13, 2024
dsolistorres
pushed a commit
that referenced
this issue
Sep 18, 2024
### Proposed Changes * Emit the initial value of the form in `workflowsSelected$` observable. * Add a check to ensure the workflow actions dropdown exists before attempting to clear it. ### Checklist - [x] Tests - [x] Translations - [x] Security Implications Contemplated (add notes if applicable) ### Additional Info This PR fixes: 1. #29765 2. #29762 ### Screenshots #### Before ![image](https://github.com/user-attachments/assets/f9851368-7479-4a9c-a354-77c82093a0c9) #### After https://github.com/user-attachments/assets/766cb82a-763f-4d57-8325-14eaba622455
Approved: Tested on trunk_5b70657, Docker, macOS 14.5, FF v126.0.1 |
josemejias11
moved this from QA - In Progress
to QA - Rejected
in dotCMS - Product Planning
Sep 19, 2024
github-project-automation
bot
moved this from Done
to Internal QA
in dotCMS - Product Planning
Sep 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Parent Issue
Problem Statement
found while testing #28684
In the Content Types Update dialog, after selecting a Default Action and clicking the "Update" button, the dialog closes as expected. However, if you reopen the dialog, it appears unchanged, as if the modifications were not saved. Despite this, a deeper investigation reveals that the changes are indeed saved. When checking the API response from the "API" button on the main Content Types edit screen, the JSON representation of the Content-Type reflects the saved changes. Additionally, if you use the CLI to download the Content Type definition, the JSON correctly shows the updates, including the changes to the Default Action. This behavior suggests that the UI is ignoring the presence of the systemActionMappings attribute in the server's response, leading to the false impression that the changes were not applied.
Steps to Reproduce
Screen.Recording.2024-08-27.at.12.38.36.PM.mov
Acceptance Criteria
The Dialog must show accurate saved data
dotCMS Version
current Trunk. it can also be reproduced in demo
Proposed Objective
User Experience
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: