Bug #18696
closed[RFE] add confirmation step for manifest deletion (explaining when refresh will do, and when have to use delete)
Description
Cloned from BZ:
Description of problem:
It's reported that oftentimes customers delete manifest when trying to update subscriptions / upload a newer manifest, in which case all that's needed is a Refresh, and deletion would cause problems by losing/disconfiguring server and client subscriptions etc. The only times where manifest needs to be deleted includes when a Satellite server is no longer active or the manifest has been removed from the Customer Portal.
A confirmation step will address this confusion by explaining to users refresh vs delete and asking if they're sure they want to delete manifest or just go back and refresh it.
Version-Release number of selected component (if applicable):
Satellite 6
Updated by Brad Buckingham almost 8 years ago
- Target version changed from 169 to 178
Updated by Chris Roberts almost 8 years ago
- Assignee changed from Chris Roberts to Brad Buckingham
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Translation missing: en.field_release deleted (
114) - Pull request https://github.com/Katello/katello/pull/6711 added
Updated by Brad Buckingham almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|367b534fa1fbe009e45282cf55baa27a4bd2546f.
Updated by Eric Helms over 7 years ago
- Translation missing: en.field_release set to 211