-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Reusable blocks: Bad UX for non-privileged users #12338
Copy link
Copy link
Closed
Labels
[Feature] Synced PatternsRelated to synced patterns (formerly reusable blocks)Related to synced patterns (formerly reusable blocks)[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] BugAn existing feature does not function as intendedAn existing feature does not function as intended
Milestone
Metadata
Metadata
Assignees
Labels
[Feature] Synced PatternsRelated to synced patterns (formerly reusable blocks)Related to synced patterns (formerly reusable blocks)[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] BugAn existing feature does not function as intendedAn existing feature does not function as intended
Type
Fields
Give feedbackNo fields configured for issues without a type.
There are some very rough edges when using, creating and modifying reusable blocks as an author or contributor. I've summarised the issues here as it's easier to address them as one task.
Creating a reusable block as a contributor
Expected: The Add to Reusable Blocks button should be disabled.
Actual: The Add to Reusable Blocks button is enabled. Clicking it results in an error notice appearing when the API request fails.
Updating another user's reusable block as an author
Expected: The Edit button should be disabled.
Actual: The Edit button is enabled. Clicking it lets you edit the block and save changes which results in an error notice appearing when the API request fails.
Deleting another user's reusable block as an author or contributor
Expected: The Remove from Reusable Blocks button should be disabled.
Actual: The Remove from Reusable Blocks button is enabled. Clicking it results in an error notice appearing when the API request fails.