Bug 749560 - make it clear to user what "delete" bundle will do
Summary: make it clear to user what "delete" bundle will do
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI, Provisioning
Version: 4.2
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: ---
: JON 3.0.0,RHQ 4.3.0
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-27 14:05 UTC by John Mazzitelli
Modified: 2012-02-07 19:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description John Mazzitelli 2011-10-27 14:05:55 UTC
When a user elects to "delete" a bundle, we need to be clear what they are asking it to do - we only delete the database entities. We do not purge data off the remote agent boxes - that's what the purge button does.

We need to go through the bundle UI and everywhere we supply a delete button, we need to make sure the confirmation dialog that pops up when you press it tells the user about what it is going to do.  Don't just say, "Are you sure you want to delete" because it isn't going to be clear to people that it isn't really purging the content from the remote boxes.

Comment 1 John Mazzitelli 2011-10-27 16:22:34 UTC
These are the new confirmation messages. We should get our i18n translations fixed for these.

view_bundle_list_deleteConfirm = Are you sure you want to delete the selected bundles? This will delete all of their versions, destinations and deployments from the database. However, this will not remove any content from remote machines.

view_bundle_deleteConfirm = Are you sure you want to delete this bundle? All versions, destinations and deployments for this bundle will also be deleted. However, this will not remove any content from remote machines.

view_bundle_version_deleteConfirm = Are you sure you want to delete this bundle version? This will not remove any content from remote machines.

view_bundle_deploy_deleteConfirm = Are you sure you want to delete this bundle deployment? This only deletes it from the database; all bundle content that was deployed on remote machines will remain.

Comment 2 John Mazzitelli 2011-10-27 16:24:05 UTC
this is on a local branch on my box, will push when master is unfrozen

Comment 3 Heiko W. Rupp 2011-10-27 19:09:47 UTC
This is good, as I was hesitant to translate delete & purge into German, as it was not clear to me what the difference was.

I wonder if the wording of 'delete' and 'purge' on the buttons could be relabeled to something along "delete in db" and "undeploy & delete in db"

Comment 4 John Mazzitelli 2011-11-01 13:49:04 UTC
git commit:
release_jon3.x: a94a8992b37b10a4224eef050911dd6759a7705e
master: 4821904bdbf4c53071c9f1fb5cdacfa0aa4c6f85

Comment 5 Sunil Kondkar 2011-11-02 10:23:33 UTC
Verified on build#672 (Version: 4.3.0-SNAPSHOT Build Number: ca0281f)

Verified delete confirmation messages in bundle UI. Below are the messages:

1. Selecting a bundle and click on 'Delete' button in bundle list view:

Are you sure you want to delete the selected bundles? This will delete all of their versions, destinations and deployments from the database. However, this will not remove any content from remote machines.

2. Navigate inside a bundle and click on the 'Delete' button.

Are you sure you want to delete this bundle? All versions, destinations and deployments for this bundle will also be deleted. However, this will not remove any content from remote machines

3. Click on the 'Delete' button in a bundle version:

Are you sure you want to delete this bundle version? This will not remove any content from remote machines.

4. Click the 'Delete' button inside the deployment view:

Are you sure you want to delete this bundle deployment? This only deletes it from the database; all bundle content that was deployed on remote machines will remain.

5. Click 'Delete' button in the destination view:

Are you sure you want to delete this bundle destination? This only deletes it from the database; all bundle content that was deployed to this destination on remote machines will remain.

Comment 6 Mike Foley 2012-02-07 19:26:04 UTC
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE

Comment 7 Mike Foley 2012-02-07 19:31:44 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


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