Bug 1117760
| Summary: | Browse button does not work for first time - pattern-fly ui | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Armine Hovsepyan <ahovsepy> | ||||
| Component: | UI, Usability | Assignee: | Jirka Kremser <jkremser> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | JON 3.2 | CC: | hrupp, jkremser, lzoubek, mfoley | ||||
| Target Milestone: | DR01 | ||||||
| Target Release: | JON 3.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-12-11 14:00:18 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1116784 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
change (132e2f1f0fa5d31bec3c2743da884d1423ae357d) is in master Setting on modified as it is in release/jon3.3.x Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993 verified on DR1 |
Created attachment 916714 [details] browse-file Description of problem: Browse button does not work for first time - pattern-fly ui Version-Release number of selected component (if applicable): rhq 4.12 master build id: 1a62d13 How reproducible: always Steps to Reproduce: 1. create child resource with deployment type for EAP6 2. Browse war file 3. Browse war file again Actual results: browse file does not work for the first time - file is not browsed Expected results: browse file works from the first time Additional info: video with reproduction steps attached not a blocking issue, but from usability perspective is annoying - marking as high severity