It must be possible to open a case for an EAP server that is managed by JON.
JON must pull the JDR data from the server and forward it to the CSP
Heiko Rupp <email@example.com> updated the status of jira JON3-12 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
Created attachment 923015 [details]
rha support is not built. see attached.
mfoley user <firstname.lastname@example.org> updated the status of jira JON3-12 to Reopened
Mike, is this still an issue, has the feature been well defined for you? If so, please close or set MODIFIED for ER03. If not please assign/work with Libor for ER03.
testing status as or ER02 ...
4 tests. 2 fail. 2 blocked.
Moving to ON_QA as available for test with the following brew build:
Moving into ER05 as didn't make the ER04 cut.
Documenting JON3-12 test results in JON 3.3 ER04
TCMS testcase run https://tcms.engineering.redhat.com/run/185016/
Blocking BZ (also blocking for JON3-11)
JON 3-11 and JON 3-12 are failed QE in ER04.
*** Bug 1008030 has been marked as a duplicate of this bug. ***
Moving to ON_QA as available to test with latest brew build:
mfoley user <email@example.com> updated the status of jira JON3-12 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 985636 [details]
unable to attach jdr report with firstname.lastname@example.org
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 992159 [details]
Created attachment 992161 [details]
verified in JON 3.3.1 CR1
screen-shots of cases containing JDR reports attached
BZ depends on JON3-11 and 1168373, moving back to ON_QA until those 2 are verified/closed
Moving back to verified. No longer depends On: 1168373. JON3-11 is verified.