Hide Forgot
Description of problem: If you remove the only destination of a bundle which has multiple deployments, that bundle is no longer visible in the left nav bundle view. This isn't consistent with the behavior on an initial deploy without the destination (ie. the bundle is visible in the left nav even though it doesn't have a destination). Version-Release number of selected component (if applicable): JON 3.0.0.GA How reproducible: Steps to Reproduce: 1. Multiple deployments to the same destination 2. Only specify 1 destination 3. Remove that destination by highlight destinations grouping and clicking "delete" Actual results: Expected results: Additional info:
If the bundle is still available, somewhere in the UI, then I agree its low.
per BZ triage (crouch, mfoley, loleary). setting priority to medium, no target release.
Testing this on RHQ 4.6.0, I could not reproduce. If one clicks on the destination name in the left nav and then clicks "Delete" in the detail of the destination in the right pane, it is successfully deleted and the bundle itself remains in the left nav. What might have happened is that Andy clicked on the "Destinations" in left nav, i.e. the parent node of all destinations in the tree. Clicking on this brings up the detail page of the bundle itself and focuses on the "Destinations" tab in the right pane. The delete button on that page refers to the bundle itself! It is after all the bundle detail page. So clicking the delete button will delete the bundle itself, which would be consistent with what Andy is reporting. While that functionality might be slightly confusing to the user, the deletion of the bundle is further protected by a confirmation message box, where the user needs to explicitly confirm they approve the deletion of the bundle. I am closing this BZ, because the system works as designed, but I've raised a new RFE BZ 916205 to maybe change the way we present the information by not making the "Destinations" and "Versions" nodes in the left nav clickable so that a situation like this cannot confuse the users.