Bug 1316073 - move lifecycle_env select box from edit page to show page
Summary: move lifecycle_env select box from edit page to show page
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Shlomi Zadok
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 11:16 UTC by Kedar Bidarkar
Modified: 2019-09-26 13:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 21:18:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kedar Bidarkar 2016-03-09 11:16:07 UTC
Description of problem:

Currently the user sees the synchronize button in the 'overview tab' of the capsule show page, but has no
way of knowing that he need to add "life-cycle env" prior to synchronizing it, or where/how he needs to associate it.

a) show page and edit page needs to be unified or
b) how about we move the lifecycle-env select box near to the Capsule "synchronize button"? I feel this would help
a lot with the ease of use and would be very intutive. or
c) We should specify a help-tip suggesting the user to first add the necessary "life-cycle env" before
synchronization.


Version-Release number of selected component (if applicable):
Sat6.2-SNAP2

How reproducible:


Steps to Reproduce:
1. when trying to sync capsule content.
2.
3.

Actual results:
synchronize button is on capsule show page and

lifecycle_env select box is on capsule edit page.


Expected results:

It will be better to have both "synchronize button" and "lifecycle_env select box" on the same capsule show page, for ease of use , rather than they being on two different pages. 

Atleast a help-tip is a must to inform the user as to what needs to be done, before clicking the "synchronize" button.


Additional info:

Feel like asking this to be a blocker as this could be very confusing for the  user and it needs to be intuitive.

Comment 2 Bryan Kearney 2017-03-21 21:18:56 UTC
I do not believe this will be addressed int he next few releases, so I am closing this out. If you feel this was incorrect, please feel free to re-open with additional information.


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