Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1160740 - "Apply Selected" errata workflow does not have an "Are you sure?" check
Summary: "Apply Selected" errata workflow does not have an "Are you sure?" check
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Usability
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1194691
TreeView+ depends on / blocked
 
Reported: 2014-11-05 14:31 UTC by Todd Warner
Modified: 2017-02-23 20:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 05:18:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9474 0 None None None 2016-04-22 16:05:49 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Todd Warner 2014-11-05 14:31:59 UTC
Anything action that is "destructive" (anything that is not "R" in CRUD or anything not trivially reversable) needs to include an "are you sure" check. The described action does not include that check.

Steps:
* Go to a system.
* Click Errata
* Select a pile of errata
* Click on "Apply Selected"
* ...note no "Are you sure?" decision check.

Comment 1 RHEL Program Management 2014-11-05 14:43:10 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Walden Raines 2015-02-19 19:27:17 UTC
Created redmine issue http://projects.theforeman.org/issues/9474 from this bug

Comment 4 kybaker 2015-02-19 19:35:16 UTC
I'm okay with having a confirmation here because of the frequency and severity of the behavior. We should continue to use the styles consistent in the application currently as seen below. 

http://i.imgur.com/nbzVuBY.png

We should not blanket the application with confirmations for all destructive actions. This could become cumbersome very quickly. If we do want to utilize this confirmation more frequently in the long term we should give the user the option to check the box to never show them again.

Comment 6 Bryan Kearney 2015-02-20 17:04:27 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9474 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|39272de3c0c2901b4895d2fe66058d966a01dc68.

Comment 9 sthirugn@redhat.com 2015-03-06 19:01:47 UTC
Verified.

Satellite-6.1.0-RHEL-6-20150303.0

Comment 10 Bryan Kearney 2015-08-11 13:28:42 UTC
This bug is slated to be released with Satellite 6.1.

Comment 11 errata-xmlrpc 2015-08-12 05:18:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592


Note You need to log in before you can comment on or make changes to this bug.