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 <firstname.lastname@example.org> updated the status of jira JON3-11 to Resolved
It's in the master (3.3 will be based on it)
pull request #61
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 <email@example.com> updated the status of jira JON3-11 to Reopened
Moving to ON_QA as available to test in the following brew build:
Moving into ER05 as didn't make the ER04 cut.
Moving to ON_QA as available to test with latest brew build:
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 <firstname.lastname@example.org> 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 create a support case on JON with JDR , for both Jboss EAP product and JON product with JDR report
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.
time: 2015-01-29 17:36:35 +0100
author: Libor Zoubek - email@example.com
message: Bug 1160191 - Able to create New support case in JBoss ON who does not
'Manage Support Cases' permission
Updated RHA to 0.9.73. All files changed since 3.3.0.GA had to
(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:
*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]
Created attachment 992164 [details]
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.
JBoss Operations Network
Version : 3.3.0.GA Update 01
Build Number : ab9ebbd:884011b
GWT Version : 2.5.0
SmartGWT Version : 3.0p