As Carol Admin I should be able to disable the RT on Organization Level managed by Carol Admin
Description
PRDE - Story 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 CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
The Carol Admin should be able to disable the RT on Organization level, propagating this feature to tenants.
If the user is on DM UI and the Organization or Tenant has the flag disableRT as true, the user shouldn’t be able to add the realtime storage type.
If the tenant has the RT storage type and the org or tenant has the disableRT as true, the user should be able to visualize the storage type RT, he should be able to remove it but he shouldn’t be able to add it again.
If the tenant belongs to an organization with the flag disableRT enabled, it should disable on tenant level even if the tenant has the flag disableRT disabled.
04 - WHO CAN USE THIS FEATURE (USER ROLES): Carol Admin
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:
- On Carol Admin access, when editing an Organization, add a new option (checkbox) below Sql Processing only:
- Enable Realtime Storage
- The behavior of disabling the RT should be applied to all Tenants in the Organization.
- The organization has the RT disabled, the tenants under the organization will not have access to create storage type RT.
- When this options equals false, disable this option for Org Admin (tenant edit), showing the tooltip:
- Realtime Storage is disabled for this Organization.
Activity
Details
Priority
Highest
This issue was automatically transitioned to DONE after being deployed to production on Github.
https://github.com/totvslabs/carol-ui/releases/tag/v4.38.0
No associated issue on JIRA TOTVS BRAZIL.
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master 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.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
feat(org/realtimeDisabled): https://totvslabs.atlassian.net/browse/CAPL-4991#icft=CAPL-4991 https://totvslabs.atlassian.net/browse/CAPL-4993#icft=CAPL-4993 review flags behaviors
Github user carlosafw has just approved a PR (added as Shard Assignee in this Jira issue).
feat(org/realtimeDisabled): https://totvslabs.atlassian.net/browse/CAPL-4991#icft=CAPL-4991 https://totvslabs.atlassian.net/browse/CAPL-4993#icft=CAPL-4993 review flags behaviors
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.
feat(org/realtimeDisabled): https://totvslabs.atlassian.net/browse/CAPL-4991#icft=CAPL-4991 https://totvslabs.atlassian.net/browse/CAPL-4993#icft=CAPL-4993 review flags behaviors
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Andre Pasold ,
This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-12-11
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.