You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Link to existing workspaces when you can't delete a template #9348
I'd be open to this, although it may be better for us to provide a link that helps with steps "Go to workspace page," "Filter for all workspace of the template to be deleted" to ensure the admin manually reviews the workspaces that are being deleted, to avoid disrupting users. Will defer to Bruno here!
Since the bulk deletion feature is enterprise and unavailable for all the accounts, we could have a link "See all the existent workspaces for this template" redirecting the user to the workspaces page filtered by the template. Thoughts?
Going to make a quick Figma mock-up and maybe even try to have the full PR done today, but in the meantime @bpmct, do you have any preferences on whether anything should change for users who do have access to bulk-deletion?
What I'm thinking right now is that when a user has workspaces using a template:
The deletion box and delete button should actually be hidden completely. Don't even give the user the chance to try a deletion that will fail anyway
Instead show a message that tells them they have workspaces that need to be deleted, as well as a link that:
Takes them to the workspaces page
Pre-fills the search input so that they see the relevant workspaces immediately
If a user has access to bulk-deletion, would you also like some kind of button/input to be made visible alongside the link?
The deletion box and delete button should actually be hidden completely. Don't even give the user the chance to try a deletion that will fail anyway
By doing that, the user has no chance to understand why it is happening.
Instead show a message that tells them they have workspaces that need to be deleted, as well as a link that:
I would not redirect the user directly without their knowing why. Showing a message like "You are not able to delete this template because there are workspaces using it. [See all workspaces using this template]" looks like a better and more predictive option IMO
If a user has access to bulk-deletion, would you also like some kind of button/input to be made visible alongside the link?
Oh, sorry. That was a part I omitted. Basically, the way I'm thinking about it is that there's two states the modal could be in (ignoring the states already in place):
There are workspaces linked to the template
There aren't
If there aren't any, we just use the same UI as before, and the experience doesn't change.
But if there are, the following would change:
The text input and delete button disappear
A new message appears (styled as a warning) saying that the user has workspaces. Inside that message is a link to the workspaces page, but the link also has search params set, so the moment the user navigates, they see the workspaces linked to the template right away, without any need to do more typing. There wouldn't ever be automatic navigation – the user has to initiate everything
And then for the other question, basically, I'm wondering if it's worth trying to reduce friction further if the user has access to bulk-deletion. As in, rather than making them jump to the workspaces page, instead add one extra element/input set that lets the user do the bulk deletion directly from the modal. I do think that there's such a thing as too little UX friction (especially for destructive actions), though, so I'm not sure if this might be going too far
Activity
matifali commentedon Sep 1, 2023
This is related to a request in #9473 to allow deleting a template along with all it's workspace in bulk.
As we already have bulk deleting capability now. I guess a simple implementation can be
Thoughts @BrunoQuaresma @bpmct
PS:
It can be done manually quite easily but that includes manual steps
bpmct commentedon Sep 5, 2023
I'd be open to this, although it may be better for us to provide a link that helps with steps "Go to workspace page," "Filter for all workspace of the template to be deleted" to ensure the admin manually reviews the workspaces that are being deleted, to avoid disrupting users. Will defer to Bruno here!
matifali commentedon Sep 5, 2023
@bpmct I guess you mean this workflow
BrunoQuaresma commentedon Sep 5, 2023
Since the bulk deletion feature is enterprise and unavailable for all the accounts, we could have a link "See all the existent workspaces for this template" redirecting the user to the workspaces page filtered by the template. Thoughts?
matifali commentedon Sep 5, 2023
@BrunoQuaresma, I like it.
buenos-nachos commentedon Oct 6, 2023
Going to make a quick Figma mock-up and maybe even try to have the full PR done today, but in the meantime @bpmct, do you have any preferences on whether anything should change for users who do have access to bulk-deletion?
What I'm thinking right now is that when a user has workspaces using a template:
If a user has access to bulk-deletion, would you also like some kind of button/input to be made visible alongside the link?
BrunoQuaresma commentedon Oct 6, 2023
By doing that, the user has no chance to understand why it is happening.
I would not redirect the user directly without their knowing why. Showing a message like "You are not able to delete this template because there are workspaces using it. [See all workspaces using this template]" looks like a better and more predictive option IMO
I didn't understand this part.
buenos-nachos commentedon Oct 6, 2023
Oh, sorry. That was a part I omitted. Basically, the way I'm thinking about it is that there's two states the modal could be in (ignoring the states already in place):
If there aren't any, we just use the same UI as before, and the experience doesn't change.
But if there are, the following would change:
And then for the other question, basically, I'm wondering if it's worth trying to reduce friction further if the user has access to bulk-deletion. As in, rather than making them jump to the workspaces page, instead add one extra element/input set that lets the user do the bulk deletion directly from the modal. I do think that there's such a thing as too little UX friction (especially for destructive actions), though, so I'm not sure if this might be going too far
BrunoQuaresma commentedon Oct 6, 2023
I would go with simple first, try it do some QA, and see how it feels. If you think it is bad or meh, you can work on improvements.