It must be possible to open JON cases on the CSP from within JON
See also https://bugzilla.redhat.com/show_bug.cgi?id=1069547#c1
Heiko Rupp <hrupp> updated the status of jira JON3-11 to Resolved
It's in the master (3.3 will be based on it) pull request #61 commits: 4012346e0 c49d37318 5a50fe270 63815b9e5 ce94b7c59 2eb8b5923 20d1821f3 1c2cea1c2 0979d143e 53cb140de 6876f8593 4eaddf84e 871942c5e
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
I need to reject this BZ. The requirement is not met. See attached screenshot. rha support war was not built.
Created attachment 923014 [details] JON 3-11 fails QE
mfoley user <mfoley> updated the status of jira JON3-11 to Reopened
Moving to ON_QA as available to test in the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=379025
Moving into ER05 as didn't make the ER04 cut.
Moving to ON_QA as available to test with latest brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=396547
This is the testing status of this feature in CR01 (which is a GA candidate). New bugs ...as well as fail-to-verify https://bugzilla.redhat.com/show_bug.cgi?id=1160191 JON 3-11, JON 3-12 ....would require a new RHA .war file https://bugzilla.redhat.com/show_bug.cgi?id=1133590 JON 3-11, JON 3-12 would require a new RHA .war file https://bugzilla.redhat.com/show_bug.cgi?id=1134829 JON 3-11, JON3-12 would require a new RHA .war file This tracker has outlived it usefulness. We are going to GA with some issues and requirements on this feature not met. I can't set this to VERIFIED ...(as it is not). setting to RELEASE PENDING
mfoley user <mfoley> updated the status of jira JON3-11 to Resolved
Removing "Tracker" from title as this is not a tracker. Instead, this is an actual requirement that was submitted and partially implemented for JBoss ON 3.3. As QE indicated that testing was incomplete at the time of GA, they had moved this to an invalid state. Moving back to ON_QA for 3.3.z for proper testing and validation.
Created attachment 985635 [details] unable_to_attach_JDR_report
unable to create a support case on JON with JDR , for both Jboss EAP product and JON product with JDR report see attachment
below commit fixes possible caching issue of custom-cases.js which might have resulted in Invalid User/Pass when attempting to generate & attach JDR report. branch: release/jon3.3.x link: https://github.com/rhq-project/rhq/commit/22a1dad19 time: 2015-01-29 17:36:35 +0100 commit: 22a1dad1933a25bf3b4731873a663760a3436671 author: Libor Zoubek - lzoubek message: Bug 1160191 - Able to create New support case in JBoss ON who does not have 'Manage Support Cases' permission Updated RHA to 0.9.73. All files changed since 3.3.0.GA had to be renamed (prevent browser caching) added CacheFilter class which sets correct headers to returned js,css,html files - so we don't need to rename files with further updates.
Moving to ON_QA as available to test with latest CP build: http://download.devel.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/16/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip *Note: jon-server-patch-3.3.0.GA.zip maps to CR01 build of jon-server-3.3.0.GA-update-01.zip.
Created attachment 992163 [details] eap_new_case_jdr
Created attachment 992164 [details] jon-new-case-jdr
All the 'Depends On' moved to verified/Closed state, also verified able to create new support case in JON server. hence moved this bug to verified state. Version: JBoss Operations Network Version : 3.3.0.GA Update 01 Build Number : ab9ebbd:884011b GWT Version : 2.5.0 SmartGWT Version : 3.0p