Bug #18696

[RFE] add confirmation step for manifest deletion (explaining when refresh will do, and when have to use delete)

Added by Chris Roberts over 5 years ago. Updated almost 4 years ago.

Web UI
Target version:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


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

Associated revisions

Revision 367b534f (diff)
Added by Brad Buckingham over 5 years ago

fixes #18696 - add confirmation modal to 'delete manifest'

This commit adds a confirmation modal to the 'Delete Manifest'
operation in the UI.

The content of the text is derived from input received on
a downstream bugzilla, but essentially applies upstream as well.


#1 Updated by Brad Buckingham over 5 years ago

  • Target version changed from 169 to 178

#2 Updated by Chris Roberts over 5 years ago

  • Assignee changed from Chris Roberts to Brad Buckingham

#3 Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Legacy Backlogs Release (now unused) deleted (114)
  • Pull request added

#4 Updated by Brad Buckingham over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Eric Helms about 5 years ago

  • Legacy Backlogs Release (now unused) set to 211

Also available in: Atom PDF