Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28289

JNLP slave should exclude non proxy hosts when connecting via HTTP proxy

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      https://issues.jenkins-ci.org/browse/JENKINS-6167
      The fix submitted for this issue does not take into account the excluded proxy hosts unlike the hudson.remoting.Util.openURLConnection method which implicitly excludes hosts.

      A fix using the same method as sun.net.www.protocol.http.HttpURLConnection is available here :
      https://github.com/hypnoce/remoting/commit/67dbd966e628c42a0aa4d3cd91a56a00b7f95030

      Thanks

        Attachments

          Issue Links

            Activity

            hypnoce Francis JAC created issue -
            Hide
            hypnoce Francis JAC added a comment -

            Hi,

            any news on that point ? Is the fix provided suitable for a pull request ?

            Thanks

            François

            Show
            hypnoce Francis JAC added a comment - Hi, any news on that point ? Is the fix provided suitable for a pull request ? Thanks François
            Hide
            danielbeck Daniel Beck added a comment -

            Could you submit your fix as a pull request to remoting?

            Show
            danielbeck Daniel Beck added a comment - Could you submit your fix as a pull request to remoting?
            Hide
            hypnoce Francis JAC added a comment -
            Show
            hypnoce Francis JAC added a comment - Hello, done : https://github.com/jenkinsci/remoting/pull/55 Thanks.
            teilo James Nord made changes -
            Field Original Value New Value
            Remote Link This issue links to "PR#55 (Web Link)" [ 13144 ]
            Hide
            evanx9 Evan Wee added a comment -

            Would you mind resolving the conflict and resubmitting the pull request?

            Show
            evanx9 Evan Wee added a comment - Would you mind resolving the conflict and resubmitting the pull request?
            Hide
            evanx9 Evan Wee added a comment -

            I currently do not have a workaround for this.

            Show
            evanx9 Evan Wee added a comment - I currently do not have a workaround for this.
            evanx9 Evan Wee made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            evanx9 Evan Wee made changes -
            Description https://issues.jenkins-ci.org/browse/JENKINS-6167
            The fix submitted for this issue does not take into account the excluded proxy hosts unlike the hudson.remoting.Util.openURLConnection method which implicitly excludes hosts.

            A fix using the same method as sun.net.www.protocol.http.HttpURLConnection is available here :
            https://github.com/hypnoce/remoting/commit/67dbd966e628c42a0aa4d3cd91a56a00b7f95030

            Thanks
            https://issues.jenkins-ci.org/browse/JENKINS-6167
            The fix submitted for this issue does not take into account the excluded proxy hosts unlike the hudson.remoting.Util.openURLConnection method which implicitly excludes hosts.

            A fix using the same method as sun.net.www.protocol.http.HttpURLConnection is available here :
            https://github.com/hypnoce/remoting/commit/67dbd966e628c42a0aa4d3cd91a56a00b7f95030

            Thanks

            EDIT:
            An updated fix that resolves conflicts is here:
            https://github.com/jenkinsci/remoting/pull/62
            https://github.com/evanx9/remoting/commit/cb2ded8e8ba6a67dd5996a7ca90a2f4f133ec8eb
            evanx9 Evan Wee made changes -
            Remote Link This issue links to "PR#62 (Web Link)" [ 13170 ]
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Oleg Nenashev
            Path:
            src/main/java/hudson/remoting/Engine.java
            src/main/java/hudson/remoting/Util.java
            http://jenkins-ci.org/commit/remoting/a4cc02d33f35bf7ba04b58a36fc3a683097b7a9e
            Log:
            Merge pull request #55 from hypnoce/master

            JENKINS-28289 Ensure proxy exclusion list is used while getting proxy for JNLP clients

            Compare: https://github.com/jenkinsci/remoting/compare/bfbcfb3282d9...a4cc02d33f35

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/remoting/Engine.java src/main/java/hudson/remoting/Util.java http://jenkins-ci.org/commit/remoting/a4cc02d33f35bf7ba04b58a36fc3a683097b7a9e Log: Merge pull request #55 from hypnoce/master JENKINS-28289 Ensure proxy exclusion list is used while getting proxy for JNLP clients Compare: https://github.com/jenkinsci/remoting/compare/bfbcfb3282d9...a4cc02d33f35
            Hide
            geoffroyjabouley Geoffroy Jabouley added a comment - - edited

            Hello
            could this fix be included in the incoming LTS version?
            Regads

            Show
            geoffroyjabouley Geoffroy Jabouley added a comment - - edited Hello could this fix be included in the incoming LTS version? Regads
            Hide
            danielbeck Daniel Beck added a comment -

            There has not been a release of the library yet, and that release first needs to be in mainline Jenkins to soak before it can be included in LTS.

            As the release candidate for 1.625.3 is next Wednesday, this change is ineligible for inclusion in that release unless someone expedites it by pointing to some urgency.

            Maybe towards the next LTS base line for release in January.

            Show
            danielbeck Daniel Beck added a comment - There has not been a release of the library yet, and that release first needs to be in mainline Jenkins to soak before it can be included in LTS. As the release candidate for 1.625.3 is next Wednesday, this change is ineligible for inclusion in that release unless someone expedites it by pointing to some urgency. Maybe towards the next LTS base line for release in January.
            Hide
            danielbeck Daniel Beck added a comment -

            Oleg Nenashev Does the merged PR resolve this issue?

            Show
            danielbeck Daniel Beck added a comment - Oleg Nenashev Does the merged PR resolve this issue?
            danielbeck Daniel Beck made changes -
            Labels lts-candidate
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I think so

            Show
            oleg_nenashev Oleg Nenashev added a comment - I think so
            Hide
            danielbeck Daniel Beck added a comment -

            Assuming this is resolved and just an oversight in the commit message.

            Show
            danielbeck Daniel Beck added a comment - Assuming this is resolved and just an oversight in the commit message.
            danielbeck Daniel Beck made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            olivergondza Oliver Gondža made changes -
            Labels lts-candidate 1.625.3-rejected lts-candidate
            Hide
            olivergondza Oliver Gondža added a comment - - edited

            I am rejecting this is a candidate against 1.625.3 as #55 was not released (jenkinsci/remoting) and therefore not in Jenkins core. #62 was not merged yet.

            Daniel Beck, Is it really resolved if none of the changes are in core until today?

            Show
            olivergondza Oliver Gondža added a comment - - edited I am rejecting this is a candidate against 1.625.3 as #55 was not released (jenkinsci/remoting) and therefore not in Jenkins core. #62 was not merged yet. Daniel Beck , Is it really resolved if none of the changes are in core until today?
            Hide
            danielbeck Daniel Beck added a comment -

            Good question. In general, resolved does not mean released as it's the commit that matters. Of course with library/framework changes, this means it may never make it into the software as the component version also needs to be increased.

            Show
            danielbeck Daniel Beck added a comment - Good question. In general, resolved does not mean released as it's the commit that matters. Of course with library/framework changes, this means it may never make it into the software as the component version also needs to be increased.
            Hide
            evanx9 Evan Wee added a comment -

            Hi, please ignore #62 as #55 has been redone and merged.

            Would appreciate if jenkinsci/remoting could release a new version.

            Show
            evanx9 Evan Wee added a comment - Hi, please ignore #62 as #55 has been redone and merged. Would appreciate if jenkinsci/remoting could release a new version.
            evanx9 Evan Wee made changes -
            Remote Link This issue links to "PR#62 (Web Link)" [ 13170 ]
            evanx9 Evan Wee made changes -
            Description https://issues.jenkins-ci.org/browse/JENKINS-6167
            The fix submitted for this issue does not take into account the excluded proxy hosts unlike the hudson.remoting.Util.openURLConnection method which implicitly excludes hosts.

            A fix using the same method as sun.net.www.protocol.http.HttpURLConnection is available here :
            https://github.com/hypnoce/remoting/commit/67dbd966e628c42a0aa4d3cd91a56a00b7f95030

            Thanks

            EDIT:
            An updated fix that resolves conflicts is here:
            https://github.com/jenkinsci/remoting/pull/62
            https://github.com/evanx9/remoting/commit/cb2ded8e8ba6a67dd5996a7ca90a2f4f133ec8eb
            https://issues.jenkins-ci.org/browse/JENKINS-6167
            The fix submitted for this issue does not take into account the excluded proxy hosts unlike the hudson.remoting.Util.openURLConnection method which implicitly excludes hosts.

            A fix using the same method as sun.net.www.protocol.http.HttpURLConnection is available here :
            https://github.com/hypnoce/remoting/commit/67dbd966e628c42a0aa4d3cd91a56a00b7f95030

            Thanks

            Hide
            evanx9 Evan Wee added a comment -

            Daniel Beck Any prospects for this fix to be released via a new jenkinsci/remoting module?

            Show
            evanx9 Evan Wee added a comment - Daniel Beck Any prospects for this fix to be released via a new jenkinsci/remoting module?
            Hide
            danielbeck Daniel Beck added a comment -

            Sending a homing pidgeon to Oleg Nenashev so he can answer this.

            Show
            danielbeck Daniel Beck added a comment - Sending a homing pidgeon to Oleg Nenashev so he can answer this.
            olivergondza Oliver Gondža made changes -
            Labels 1.625.3-rejected lts-candidate 1.625.3-rejected 1.642.2-rejected lts-candidate
            Hide
            olivergondza Oliver Gondža added a comment -

            Release still pending.

            Show
            olivergondza Oliver Gondža added a comment - Release still pending.
            Hide
            geoffroyjabouley Geoffroy Jabouley added a comment -

            Just for clarification:
            how do we set the proxy exclusion list with this patch? Is the environment variable "no_proxy" enought, or do we have to provide a "-Dhttp.nonProxyHosts" java system property when starting the jenkins slave?
            Looking forward a new release in a LTS version

            Show
            geoffroyjabouley Geoffroy Jabouley added a comment - Just for clarification: how do we set the proxy exclusion list with this patch? Is the environment variable "no_proxy" enought, or do we have to provide a "-Dhttp.nonProxyHosts" java system property when starting the jenkins slave? Looking forward a new release in a LTS version
            Hide
            olivergondza Oliver Gondža added a comment -

            Geoffroy Jabouley, I hope I have not confused you. This was rejected for LTS inclusion again as the component was not released and integrated in Jenkins mainline.

            Show
            olivergondza Oliver Gondža added a comment - Geoffroy Jabouley , I hope I have not confused you. This was rejected for LTS inclusion again as the component was not released and integrated in Jenkins mainline.
            Hide
            geoffroyjabouley Geoffroy Jabouley added a comment -

            thanks for clarification. The sooner the better

            Show
            geoffroyjabouley Geoffroy Jabouley added a comment - thanks for clarification. The sooner the better
            Hide
            aheritier Arnaud Héritier added a comment -

            remoting 2.54 including the required fix was released 3 days ago but not yet merged into master
            PR to upgrade remoting in master: https://github.com/jenkinsci/jenkins/pull/2054

            Show
            aheritier Arnaud Héritier added a comment - remoting 2.54 including the required fix was released 3 days ago but not yet merged into master PR to upgrade remoting in master: https://github.com/jenkinsci/jenkins/pull/2054
            Hide
            olivergondza Oliver Gondža added a comment -

            Another attempt to get this into core https://github.com/jenkinsci/jenkins/pull/2074

            Show
            olivergondza Oliver Gondža added a comment - Another attempt to get this into core https://github.com/jenkinsci/jenkins/pull/2074
            olivergondza Oliver Gondža made changes -
            Labels 1.625.3-rejected 1.642.2-rejected lts-candidate 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected lts-candidate
            omar_a Omar Ahmad made changes -
            Comment [ Hi, I have chosen this week to upgrade Jenkins core to the LTS release from last month (1.642.2) and I am facing this issue when attempting to connect slaves to the master. Is there an easy way I can upgrade the remoting component from 2.53.3 to 2.56 which contains fixes, (I tried replacing the JAR in the /war/WEB-INF/lib directory but without success as the master still serves version 2.53.3), so that I can get the upgrade working? Or should I wait for the next LTS release? Thanks ]
            Hide
            geoffroyjabouley Geoffroy Jabouley added a comment -

            Hello
            do you think this fix will make its way to a jenkins 1.X LTS release before jenkins 2.0?

            Show
            geoffroyjabouley Geoffroy Jabouley added a comment - Hello do you think this fix will make its way to a jenkins 1.X LTS release before jenkins 2.0?
            Hide
            danielbeck Daniel Beck added a comment -

            Geoffroy Jabouley Not automatically, as it was only merged into 1.653, and the next LTS line is based on 1.651. But now at least there's a chance.

            Show
            danielbeck Daniel Beck added a comment - Geoffroy Jabouley Not automatically, as it was only merged into 1.653, and the next LTS line is based on 1.651. But now at least there's a chance.
            olivergondza Oliver Gondža made changes -
            Labels 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected lts-candidate 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1-fixed
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Kohsuke Kawaguchi
            Path:
            core/src/main/java/jenkins/slaves/DefaultJnlpSlaveReceiver.java
            core/src/main/java/jenkins/slaves/JnlpAgentReceiver.java
            core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol.java
            core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol2.java
            core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java
            core/src/main/java/jenkins/slaves/JnlpSlaveHandshake.java
            pom.xml
            http://jenkins-ci.org/commit/jenkins/af1a53d91c4863f27e4fad295911f131beb64b9a
            Log:
            Merge pull request #2010 from jenkinsci/jnlp3

            [FIXED JENKINS-26580][FIXED JENKINS-28289] Activate JNLP3 support
            (cherry picked from commit 6d3e05439643097d2f172761ea82a32a857d058a)

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/jenkins/slaves/DefaultJnlpSlaveReceiver.java core/src/main/java/jenkins/slaves/JnlpAgentReceiver.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol2.java core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java core/src/main/java/jenkins/slaves/JnlpSlaveHandshake.java pom.xml http://jenkins-ci.org/commit/jenkins/af1a53d91c4863f27e4fad295911f131beb64b9a Log: Merge pull request #2010 from jenkinsci/jnlp3 [FIXED JENKINS-26580] [FIXED JENKINS-28289] Activate JNLP3 support (cherry picked from commit 6d3e05439643097d2f172761ea82a32a857d058a)
            olivergondza Oliver Gondža made changes -
            Labels 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1-fixed 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1-rejected
            Hide
            olivergondza Oliver Gondža added a comment -

            Fixing this on master caused JENKINS-33886, not backporting this into LTS.

            Show
            olivergondza Oliver Gondža added a comment - Fixing this on master caused JENKINS-33886 , not backporting this into LTS.
            olivergondza Oliver Gondža made changes -
            Link This issue is related to JENKINS-33886 [ JENKINS-33886 ]
            olivergondza Oliver Gondža made changes -
            Labels 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1-rejected 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1-rejected lts-candidate
            Hide
            geoffroyjabouley Geoffroy Jabouley added a comment -

            What was at the beginning a simple patch supposed to fix a regression introduced in march 2015 (it's been a year now!) still cannot be mainlined because someone has decided instead to include it in a much wider story/task of implementing JNLP3 support.

            Why not keeping the scope of this fix simple?

            Show
            geoffroyjabouley Geoffroy Jabouley added a comment - What was at the beginning a simple patch supposed to fix a regression introduced in march 2015 (it's been a year now!) still cannot be mainlined because someone has decided instead to include it in a much wider story/task of implementing JNLP3 support. Why not keeping the scope of this fix simple?
            olivergondza Oliver Gondža made changes -
            Labels 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1-rejected lts-candidate 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1-rejected 1.651.2-fixed
            Hide
            etiennebec Etienne Bec added a comment - - edited

            Hi,

            We've upgraded to the latest LTS 1.651.2 and still experiencing issue with our proxy. The JNLP agent doesn't take in account the environment variable no_proxy nor the system proprerty http.nonProxyHosts. When http_proxy or http.proxyHost are defined it always use the proxy connection.

            To my understanding the bug was introduced as a side-effect by PR27 on remoting which proxy implementation was incomplete (it doesn't support exclusions). It actually added proxy to two methods: Launcher:parseJnlpArguments #1 and Engine:run #2.

            PR55 only fixed Engine:run, it didn't modify the Util:openURLConnection method which is now called in Launcher:parseJnlpArguments #3 (instead of URL:openConnection). As this method is immediately called after the agent is started when used with system property jnlpUrl, it also immediately failed when the connection timeouts, throws an Exception and exits at #4.

            Moreover PR55 fix only works if you use http.proxyHost property: Java reads for you http.nonProxyHosts and will update the list of proxies returned by ProxySelector.getDefault().select(<URI>). But if you use the environment variable, no_proxy is never used.

            1. https://github.com/shirosaki/remoting/blob/8c875cbc81d22df898a57ef86e833b41c50470cb/src/main/java/hudson/remoting/Launcher.java#L247
            2. https://github.com/shirosaki/remoting/blob/8c875cbc81d22df898a57ef86e833b41c50470cb/src/main/java/hudson/remoting/Engine.java#L169
            3. https://github.com/jenkinsci/remoting/pull/55/files?diff=unified
            4. https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Launcher.java#L275

            Show
            etiennebec Etienne Bec added a comment - - edited Hi, We've upgraded to the latest LTS 1.651.2 and still experiencing issue with our proxy. The JNLP agent doesn't take in account the environment variable no_proxy nor the system proprerty http.nonProxyHosts . When http_proxy or http.proxyHost are defined it always use the proxy connection. To my understanding the bug was introduced as a side-effect by PR27 on remoting which proxy implementation was incomplete (it doesn't support exclusions). It actually added proxy to two methods: Launcher:parseJnlpArguments #1 and Engine:run #2 . PR55 only fixed Engine:run , it didn't modify the Util:openURLConnection method which is now called in Launcher:parseJnlpArguments #3 (instead of URL:openConnection ). As this method is immediately called after the agent is started when used with system property jnlpUrl , it also immediately failed when the connection timeouts, throws an Exception and exits at #4 . Moreover PR55 fix only works if you use http.proxyHost property: Java reads for you http.nonProxyHosts and will update the list of proxies returned by ProxySelector.getDefault().select(<URI>). But if you use the environment variable, no_proxy is never used. 1. https://github.com/shirosaki/remoting/blob/8c875cbc81d22df898a57ef86e833b41c50470cb/src/main/java/hudson/remoting/Launcher.java#L247 2. https://github.com/shirosaki/remoting/blob/8c875cbc81d22df898a57ef86e833b41c50470cb/src/main/java/hudson/remoting/Engine.java#L169 3. https://github.com/jenkinsci/remoting/pull/55/files?diff=unified 4. https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Launcher.java#L275
            Hide
            etiennebec Etienne Bec added a comment -

            We're still experiencing the issue. See my last comment.

            Show
            etiennebec Etienne Bec added a comment - We're still experiencing the issue. See my last comment.
            etiennebec Etienne Bec made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            Hide
            danielbeck Daniel Beck added a comment -

            Etienne Bec To clarify, this issue is fixed as described, but you're using yet another environment variable, and that one isn't used?

            Show
            danielbeck Daniel Beck added a comment - Etienne Bec To clarify, this issue is fixed as described, but you're using yet another environment variable, and that one isn't used?
            Hide
            etiennebec Etienne Bec added a comment - - edited

            I will give you some background. Our network is behind a corporate proxy and thus we need to go through it to access to Internet. That's why we have defined the two standard environment variables, http_proxy and no_proxy, to configure several tools (curl for instance), to use the proxy. The slaves and the master are on the same network so they can communicate directly, that's why we didn't set the system properties http.proxyHost and so on.

            We were previously running Jenkins 1.596.3 which uses remoting 2.47, and this version doesn't include the PR27. And with this PR the trouble begins because the slave started to take in account only the first env var I mentioned: http_proxy. no_proxy is never read. And the PR55 which is related to this issue doesn't fix this either. It just introduced the use of ProxySelector which automatically take in account the exception list ... defined by the system property http.nonProxyHosts. And as in the PR27 it reads the http_proxy env var as a fallback, but doesn't use no_proxy at all!

            To be more clear, we don't use the proxy features on our side. It's just that the slave started with the PR27 to read some env var it should not (because that's not how the JVM should be configured). So either we need to take in account no_proxy or we remove from the two methods the part which use http_proxy: https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114 & https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114.

            I've reopened this issue because to my understanding the goal of this issue wasn't just to add the support for http.nonProxyHosts but to correct PR27. Should we create a new issue?

            Show
            etiennebec Etienne Bec added a comment - - edited I will give you some background. Our network is behind a corporate proxy and thus we need to go through it to access to Internet. That's why we have defined the two standard environment variables, http_proxy and no_proxy , to configure several tools (curl for instance), to use the proxy. The slaves and the master are on the same network so they can communicate directly, that's why we didn't set the system properties http.proxyHost and so on. We were previously running Jenkins 1.596.3 which uses remoting 2.47, and this version doesn't include the PR27. And with this PR the trouble begins because the slave started to take in account only the first env var I mentioned: http_proxy . no_proxy is never read. And the PR55 which is related to this issue doesn't fix this either. It just introduced the use of ProxySelector which automatically take in account the exception list ... defined by the system property http.nonProxyHosts . And as in the PR27 it reads the http_proxy env var as a fallback, but doesn't use no_proxy at all! To be more clear, we don't use the proxy features on our side. It's just that the slave started with the PR27 to read some env var it should not (because that's not how the JVM should be configured). So either we need to take in account no_proxy or we remove from the two methods the part which use http_proxy : https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114 & https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114 . I've reopened this issue because to my understanding the goal of this issue wasn't just to add the support for http.nonProxyHosts but to correct PR27. Should we create a new issue?
            Hide
            danielbeck Daniel Beck added a comment -

            Probably best as a separate issue. This one has too much history IMO.

            Show
            danielbeck Daniel Beck added a comment - Probably best as a separate issue. This one has too much history IMO.
            Hide
            etiennebec Etienne Bec added a comment - - edited

            Looks like it has already been reported: https://issues.jenkins-ci.org/browse/JENKINS-32326

            I will mark this issue as resolved.

            Show
            etiennebec Etienne Bec added a comment - - edited Looks like it has already been reported: https://issues.jenkins-ci.org/browse/JENKINS-32326 I will mark this issue as resolved.
            etiennebec Etienne Bec made changes -
            Status Reopened [ 4 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 163123 ] JNJira + In-Review [ 197107 ]

              People

              • Assignee:
                Unassigned
                Reporter:
                hypnoce Francis JAC
              • Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: