| Summary: | Need inline help text | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Og Maciel <omaciel> | ||||
| Component: | WebUI | Assignee: | Bryan Kearney <bkearney> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Katello QA List <katello-qa-list> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.1 | CC: | bkearney, mmccune | ||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-09-19 18:15:36 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
mass move to CFSE product. I am working on it. Proposed solution for forms: https://github.com/Katello/katello/pull/406 getting rid of 6.0.0 version since that doesn't exist These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM. If this is a mistake feel free to re-open. |
Created attachment 542713 [details] Adding a system Description of problem: As an end user, there are certain areas of the web ui where you're faced with forms that provide no help, tooltip, or useful information as far as what each field really means, what kind of data is expected and if the field is required or not. I am attaching a screenshot here for a very specific case, but will gladly add more screenshots of different areas if someone feels that it's ok to have a "global" issue for these kinds of cases. Otherwise, I could file separate tickets too. The screenshot shows the panel for adding a new system. None of the fields are "flagged" as required. Also, if you don't know what "Number of Sockets or LPARs" mean, there's no (obvious) easy way to obtain that information. I'd make the case that each label for a field should be a link to a pop-up/tooltip/dialog containing help text that explains the meaning of it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: