No confirmation asked for when making a private snap public
Bug #1746364 reported by
Lyubomir Popov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snap Store Server |
Fix Released
|
Low
|
Ricardo Kirkner | ||
Bug Description
It is too easy to make a private snap public. It doesn't require any sort of confirmation, and even though it is easy to revert, customers felt let down by the lack of a confirm step.
Reported by Nick Zatkovich, CTO of RosHub (roshub.com)
| description: | updated |
| description: | updated |
Revision history for this message
| Nicholas Zatkovich (nickz-roshub) wrote | #1 |
| tags: | added: design |
| Changed in snapstore: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in snapstore: | |
| assignee: | nobody → Ricardo Kirkner (ricardokirkner) |
| status: | Confirmed → Fix Committed |
| status: | Fix Committed → In Progress |
| Changed in snapstore: | |
| status: | In Progress → Fix Committed |
| Changed in snapstore: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
To be clear, I just don't want to be able to accidentally make the snap public so easily. I was fortunate that when it happened, I caught it and was immediately able to revert it, but I think a confirmation box for this would obviate this problem.