[Updated by Myriam 26/07/2018]
The ask checkbox in BOM is supposed to dictate whether or not I get asked for confirmation before I delete a product.
Currently I get asked for confirmation (regardless of the ASK checkbox's state) when I delete using the trash can button.
When I delete by selecting product checkboxes and delete by going Actions > Delete Selected, I'm never asked for confirmation.
All these behaviours are confusing and unconsistent and get users lost.

We raised the deletion UX topic again while working an the image deletion issue.
S3, a bit disturbing on UX side and dangerous for the bulk action not to have the confirmation popin
Hey,
We've had a couple of users over in the UK having issues with this button too.
Just want to check in regarding the assignment of this issue and whether we can look to getting a quick fix? Either removing it or having the functionality put behind it?
I also wonder if there is better terminology that we could use rather than Ask? Or perhaps we can have a tooltip that explains what "Ask" does so the users isn't tempted to toggle it on and off without know the implications.
Cheers,
Sinead
I also wonder if there is better terminology that we could use rather than Ask?
Totally agree. A user trying out our local instance had the same problem because it's not clear what is that checkbox about. I suggest we replace it with a better copy.
Hi, here is my 2cents to the subject, I believe the most intuitive UI would be to not have that checkbox. It is hard to summarize the behaviour ' do not ask for future deletes' with just the workd 'ask'.
I think for users that want to do multiple deletes, it is better to just select multiple items ande delete them from the Actions dropdown button. again is just my opinion.
I would agree @capiscuas. I think not having it would be the best solution all in all.
I think it also eliminates potential user error with having this ticked, deleting a load of items and not meaning to. The prompt to verify is useful
S
Would be great to have the whole "ask" feature described somewhere, like user stories. And then decide what's the best UX approach.
Good idea @enricostano , althought if the interface needs to describe or explain a feature, it's already not intuitive UX-wise.
@capiscuas I think @enricostano meant for us to use in the redesign of the feature, rather than as something to display for the user 馃槃
@sineadfenton perhaps you can have a go at describing the way the feature works now and how we could possibly change it? In a user flow or with stories?
@RachL @mkllnk here is another behavior connected to the way we treat deletion. We need to have some standardized way to treat them throughout our system. So the rule would be:
@myriamboure I sure can start writing some rules. The question is where would it be the more useful ? A wiki here on github ?
FYI if you have several pop-ins appearing for confirmation (like if you do several single delete in a short period of time) your browser already ask you if you do want to see the popin or not. So I don't think we need to manage that.
@myriamboure I will write down some rules as we discussed, in the meantime if this issue is blocked, this is the behavior I would advise for :
Ok I changed the issue description given the discussion above. Is the solution proposed fine with you @sineadfenton ? @sauloperez ?
Most helpful comment
@capiscuas I think @enricostano meant for us to use in the redesign of the feature, rather than as something to display for the user 馃槃
@sineadfenton perhaps you can have a go at describing the way the feature works now and how we could possibly change it? In a user flow or with stories?