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

git plugin doesn't support branch name contains slash ("/")

    Details

    • Similar Issues:

      Description

      When a branch contains slash , if we try to specify such a branch in "Branch Name" field, it will not be able to fetch such branches. If we leave branch name as **, the job can fetch branch name containing slash without problem.

      I am not a Java person, but this method looks suspicious in Branch.java, just trying to help debug

      private static String strip(String name)

      { return name.substring(name.indexOf('/', 5) + 1); }

        Attachments

          Issue Links

            Activity

            hayafirst Yi Wen created issue -
            sogabe sogabe made changes -
            Field Original Value New Value
            Link This issue is duplicated by JENKINS-9945 [ JENKINS-9945 ]
            Hide
            tsondergaard tsondergaard added a comment -

            I'm on jenkins 1.467 and with git plugin version 1.1.19 I get the following error. After downgrading to version 1.1.16 the problem went away. Is it the same problem as reported in this bug?

            Here's the log output with git plugin 1.1.19 and a fresh workspace:

            Started by upstream project "easyviz-5-integrate" build number 21
            [EnvInject] - Loading node environment variables.
            Building remotely on bob-w7-64 in workspace c:\jenkins\workspace\easyviz-5-integrate\arch\win32
            Checkout:win32 / c:\jenkins\workspace\easyviz-5-integrate\arch\win32 - hudson.remoting.Channel@2f860a43:bob-w7-64
            Using strategy: Default
            Last Built Revision: Revision d7e55522feb251a876a5e8c1d1370686b77db1b5 (origin/for-5.0.0/bug-14364-build-manual)
            Fetching changes from 1 remote Git repository
            Fetching upstream changes from ssh://builduser@git.medical-insight.com/var/git/easyviz.git
            Pruning obsolete local branches
            Commencing build of Revision e3e816d8d00386d76bfb615044c0acf1fa89f963 (origin/for-5.0.0/bug-14466-cppcheck)
            Merging Revision e3e816d8d00386d76bfb615044c0acf1fa89f963 (origin/for-5.0.0/bug-14466-cppcheck) onto release/5.0.0
            FATAL: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse origin/release/5.0.0^^{commit}" returned status code 128:
            stdout: origin/release/5.0.0^^{commit}

            stderr: fatal: ambiguous argument 'origin/release/5.0.0^^{commit}': unknown revision or path not in the working tree.
            Use '--' to separate paths from revisions

            hudson.plugins.git.GitException: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse origin/release/5.0.0^^{commit}" returned status code 128:
            stdout: origin/release/5.0.0^^{commit}

            stderr: fatal: ambiguous argument 'origin/release/5.0.0^^{commit}': unknown revision or path not in the working tree.
            Use '--' to separate paths from revisions

            at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:786)
            at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:748)
            at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:758)
            at hudson.plugins.git.GitAPI.revParse(GitAPI.java:261)
            at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1214)
            at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1197)
            at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180)
            at hudson.remoting.UserRequest.perform(UserRequest.java:118)
            at hudson.remoting.UserRequest.perform(UserRequest.java:48)
            at hudson.remoting.Request$2.run(Request.java:287)
            at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
            at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
            at java.util.concurrent.FutureTask.run(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at hudson.remoting.Engine$1$1.run(Engine.java:60)
            at java.lang.Thread.run(Unknown Source)

            Show
            tsondergaard tsondergaard added a comment - I'm on jenkins 1.467 and with git plugin version 1.1.19 I get the following error. After downgrading to version 1.1.16 the problem went away. Is it the same problem as reported in this bug? Here's the log output with git plugin 1.1.19 and a fresh workspace: Started by upstream project "easyviz-5-integrate" build number 21 [EnvInject] - Loading node environment variables. Building remotely on bob-w7-64 in workspace c:\jenkins\workspace\easyviz-5-integrate\arch\win32 Checkout:win32 / c:\jenkins\workspace\easyviz-5-integrate\arch\win32 - hudson.remoting.Channel@2f860a43:bob-w7-64 Using strategy: Default Last Built Revision: Revision d7e55522feb251a876a5e8c1d1370686b77db1b5 (origin/for-5.0.0/bug-14364-build-manual) Fetching changes from 1 remote Git repository Fetching upstream changes from ssh://builduser@git.medical-insight.com/var/git/easyviz.git Pruning obsolete local branches Commencing build of Revision e3e816d8d00386d76bfb615044c0acf1fa89f963 (origin/for-5.0.0/bug-14466-cppcheck) Merging Revision e3e816d8d00386d76bfb615044c0acf1fa89f963 (origin/for-5.0.0/bug-14466-cppcheck) onto release/5.0.0 FATAL: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse origin/release/5.0.0^^{commit}" returned status code 128: stdout: origin/release/5.0.0^^{commit} stderr: fatal: ambiguous argument 'origin/release/5.0.0^^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions hudson.plugins.git.GitException: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse origin/release/5.0.0^^{commit}" returned status code 128: stdout: origin/release/5.0.0^^{commit} stderr: fatal: ambiguous argument 'origin/release/5.0.0^^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:786) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:748) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:758) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:261) at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1214) at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1197) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source)
            Hide
            ndeloof Nicolas De Loof added a comment - - edited

            This issue is due to https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java#L73
            trying to identify a tag, the branch is not qualified as "remote" so no incoming commit is found.

            Show
            ndeloof Nicolas De Loof added a comment - - edited This issue is due to https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java#L73 trying to identify a tag, the branch is not qualified as "remote" so no incoming commit is found.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Nicolas De Loof
            Path:
            src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java
            http://jenkins-ci.org/commit/git-plugin/3b1ad202004ec3617f2023e147868876bea2e305
            Log:
            [FIXED JENKINS-14026] always add remote to branch for rev-parse
            also support multiple remotes

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java http://jenkins-ci.org/commit/git-plugin/3b1ad202004ec3617f2023e147868876bea2e305 Log: [FIXED JENKINS-14026] always add remote to branch for rev-parse also support multiple remotes
            scm_issue_link SCM/JIRA link daemon made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            Hide
            hayafirst Yi Wen added a comment -

            Thanks very much

            Show
            hayafirst Yi Wen added a comment - Thanks very much
            Hide
            arthurulfeldt arthur ulfeldt added a comment -

            a workaround for this bug is to add some other branch in the SCM checkout section then add an execute-shell build stage that switches to the branch you really want to use.

            Show
            arthurulfeldt arthur ulfeldt added a comment - a workaround for this bug is to add some other branch in the SCM checkout section then add an execute-shell build stage that switches to the branch you really want to use.
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-14480 [ JENKINS-14480 ]
            Hide
            sunyi00 Yi Sun added a comment - - edited

            jenkins 1.509.1 and jenkins git plugin 1.3.0
            this bug is still here...but can be workaround easily.

            ============================
            Branch Specifier: patch/tmp20130513/141148-7

            console log:

            git --version
            git version 1.7.10.2 (Apple Git-33)
            Fetching upstream changes from origin
            No candidate revisions
            ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
            Finished: FAILURE

            BUT if we add leading "origin/" . then it works.
            ============================
            Branch Specifier | works or not |
            master | Y |
            origin/master | Y |
            feature/test1 | N |
            origin/feature/test1| Y |

            Show
            sunyi00 Yi Sun added a comment - - edited jenkins 1.509.1 and jenkins git plugin 1.3.0 this bug is still here...but can be workaround easily. ============================ Branch Specifier: patch/tmp20130513/141148-7 console log: git --version git version 1.7.10.2 (Apple Git-33) Fetching upstream changes from origin No candidate revisions ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Finished: FAILURE BUT if we add leading "origin/" . then it works. ============================ Branch Specifier | works or not | master | Y | origin/master | Y | feature/test1 | N | origin/feature/test1| Y |
            sunyi00 Yi Sun made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            Hide
            stefanhirche Stefan Hirche added a comment -

            Hi,
            I just ran into the same issue but the "use remote" workaround does not work. But maybe I forgot something.
            I use Jenkins 1.515 with Git-Plugin 1.4.0 and Git-Client-Plugin 1.0.6.
            The branch is named release/1.0.0.0, but I get this error, also if I use origin/release/1.0.0.0:

            Fetching changes from 1 remote Git repository
            Fetching upstream changes from repoName
            No candidate revisions
            ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
            java.io.FileNotFoundException: File 'C:\.jenkins\jobs\JobName\builds\2013-05-21_16-54-50\changelog.xml.temp' does not exist
            at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:137)
            at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1102)
            at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1120)
            at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:127)
            at hudson.model.AbstractProject.checkout(AbstractProject.java:1369)
            at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
            at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
            at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
            at hudson.model.Run.execute(Run.java:1575)
            at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
            at hudson.model.ResourceController.execute(ResourceController.java:88)
            at hudson.model.Executor.run(Executor.java:241)

            So if there are any hints to my issue...

            BTW, anything is fine if I try to build branches like "master" or "develop"

            Show
            stefanhirche Stefan Hirche added a comment - Hi, I just ran into the same issue but the "use remote" workaround does not work. But maybe I forgot something. I use Jenkins 1.515 with Git-Plugin 1.4.0 and Git-Client-Plugin 1.0.6. The branch is named release/1.0.0.0, but I get this error, also if I use origin/release/1.0.0.0: Fetching changes from 1 remote Git repository Fetching upstream changes from repoName No candidate revisions ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. java.io.FileNotFoundException: File 'C:\.jenkins\jobs\JobName\builds\2013-05-21_16-54-50\changelog.xml.temp' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:137) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1102) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1120) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:127) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) So if there are any hints to my issue... BTW, anything is fine if I try to build branches like "master" or "develop"
            Hide
            stefanhirche Stefan Hirche added a comment -

            Hi,
            I just found the problem with the "remote workaround". I forgot that I renamed my remote. Using the correct remote name works.

            Show
            stefanhirche Stefan Hirche added a comment - Hi, I just found the problem with the "remote workaround". I forgot that I renamed my remote. Using the correct remote name works.
            kostmo Karl Ostmo made changes -
            Link This issue is duplicated by JENKINS-10575 [ JENKINS-10575 ]
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Vincent Latombe
            Path:
            src/main/java/hudson/plugins/git/GitSCM.java
            src/test/java/hudson/plugins/git/GitSCMTest.java
            http://jenkins-ci.org/commit/git-plugin/12b16252efb7f6ad0cb80ff04f7557b60f7bfaca
            Log:
            [FIXED JENKINS-14026] git plugin doesn't support branch name contains
            slash ("/")

            The main issue is to determine whether an input containing a slash is a
            qualified branch (remote followed by branch name) or a branch name on
            which the remote name needs to be prepended.

            When there is only one remote involved, that can be solved by prepending
            the remote name to the branch name if the branch name doesn't already
            start with the remote name.

            Note : This commit doesn't cover cases where the given branch name is a
            pattern

            Compare: https://github.com/jenkinsci/git-plugin/compare/ab720af8b26b^...12b16252efb7

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/git/GitSCM.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/12b16252efb7f6ad0cb80ff04f7557b60f7bfaca Log: [FIXED JENKINS-14026] git plugin doesn't support branch name contains slash ("/") The main issue is to determine whether an input containing a slash is a qualified branch (remote followed by branch name) or a branch name on which the remote name needs to be prepended. When there is only one remote involved, that can be solved by prepending the remote name to the branch name if the branch name doesn't already start with the remote name. Note : This commit doesn't cover cases where the given branch name is a pattern Compare: https://github.com/jenkinsci/git-plugin/compare/ab720af8b26b ^...12b16252efb7
            scm_issue_link SCM/JIRA link daemon made changes -
            Status Reopened [ 4 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Vincent Latombe
            Path:
            src/main/java/hudson/plugins/git/GitSCM.java
            src/test/java/hudson/plugins/git/GitSCMTest.java
            http://jenkins-ci.org/commit/git-plugin/13c2b08009fce7273051739acae19cfaa4d76b17
            Log:
            [FIXED JENKINS-14026] git plugin doesn't support branch name contains
            slash ("/")

            The main issue is to determine whether an input containing a slash is a
            qualified branch (remote followed by branch name) or a branch name on
            which the remote name needs to be prepended.

            When there is only one remote involved, that can be solved by prepending
            the remote name to the branch name if the branch name doesn't already
            start with the remote name.

            Note : This commit doesn't cover cases where the given branch name is a
            pattern

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/git/GitSCM.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/13c2b08009fce7273051739acae19cfaa4d76b17 Log: [FIXED JENKINS-14026] git plugin doesn't support branch name contains slash ("/") The main issue is to determine whether an input containing a slash is a qualified branch (remote followed by branch name) or a branch name on which the remote name needs to be prepended. When there is only one remote involved, that can be solved by prepending the remote name to the branch name if the branch name doesn't already start with the remote name. Note : This commit doesn't cover cases where the given branch name is a pattern
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Nicolas De loof
            Path:
            src/main/java/hudson/plugins/git/GitSCM.java
            src/test/java/hudson/plugins/git/GitSCMTest.java
            http://jenkins-ci.org/commit/git-plugin/a67bbc0062fa4dd4d27b8113f3a27840b53dded9
            Log:
            Merge pull request #187 from jenkinsci/JENKINS-14026

            [FIXED JENKINS-14026] git plugin doesn't support branch name contains

            Compare: https://github.com/jenkinsci/git-plugin/compare/b75d1e21dc75...a67bbc0062fa

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitSCM.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/a67bbc0062fa4dd4d27b8113f3a27840b53dded9 Log: Merge pull request #187 from jenkinsci/ JENKINS-14026 [FIXED JENKINS-14026] git plugin doesn't support branch name contains Compare: https://github.com/jenkinsci/git-plugin/compare/b75d1e21dc75...a67bbc0062fa
            Show
            daspilker Daniel Spilker added a comment - The fix broke the ability to checkout tags. See https://github.com/jenkinsci/git-plugin/commit/a67bbc0062fa4dd4d27b8113f3a27840b53dded9#commitcomment-5140751
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Nicolas De Loof
            Path:
            src/main/java/hudson/plugins/git/GitSCM.java
            src/test/java/hudson/plugins/git/GitSCMTest.java
            http://jenkins-ci.org/commit/git-plugin/c94ac36ff6f410ce8b7f5859b0ff9b0468a5681b
            Log:
            Revert "Merge pull request #187 from jenkinsci/JENKINS-14026"

            This reverts commit a67bbc0062fa4dd4d27b8113f3a27840b53dded9, reversing
            changes made to b75d1e21dc75c8143f99baea0342169123a409c8.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitSCM.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/c94ac36ff6f410ce8b7f5859b0ff9b0468a5681b Log: Revert "Merge pull request #187 from jenkinsci/ JENKINS-14026 " This reverts commit a67bbc0062fa4dd4d27b8113f3a27840b53dded9, reversing changes made to b75d1e21dc75c8143f99baea0342169123a409c8.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Vincent Latombe
            Path:
            src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java
            http://jenkins-ci.org/commit/git-plugin/ea5cad7e2759d0c9f5ed723fe590f982b0bb818d
            Log:
            JENKINS-14026 DefaultBuildChooser should handle smartly branches with /

            When encountering a single branch containing a '/', it is either a qualified branch or a branch containing a '/'
            In the first case, the branch should start with the name of a declared remote
            Otherwise, we fall back to unqualified behaviour, and we try to match the branch name as if it was */BRANCH

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java http://jenkins-ci.org/commit/git-plugin/ea5cad7e2759d0c9f5ed723fe590f982b0bb818d Log: JENKINS-14026 DefaultBuildChooser should handle smartly branches with / When encountering a single branch containing a '/', it is either a qualified branch or a branch containing a '/' In the first case, the branch should start with the name of a declared remote Otherwise, we fall back to unqualified behaviour, and we try to match the branch name as if it was */BRANCH
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Nicolas De loof
            Path:
            src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java
            http://jenkins-ci.org/commit/git-plugin/b22146d14997edaaf9bd95a054c65b623606d379
            Log:
            Merge pull request #195 from Vlatombe/JENKINS-14026

            JENKINS-14026 DefaultBuildChooser should handle smartly branches with /

            Compare: https://github.com/jenkinsci/git-plugin/compare/dcae49362fc1...b22146d14997

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java http://jenkins-ci.org/commit/git-plugin/b22146d14997edaaf9bd95a054c65b623606d379 Log: Merge pull request #195 from Vlatombe/ JENKINS-14026 JENKINS-14026 DefaultBuildChooser should handle smartly branches with / Compare: https://github.com/jenkinsci/git-plugin/compare/dcae49362fc1...b22146d14997
            Hide
            markewaite Mark Waite added a comment -

            Branch names containing slashes and tag based checkout are both supported since git client plugin 1.10.0 through the commit submitted by Alexander Link. The online help for the "Branches to build" field has been updated to explain the extended syntax.

            The extended syntax allows the plugin to continue supporting the old format branch specifiers and still allow specification of branch names with embedded slash characters (like develop/my-branch). The extended syntax also allows checkout of tags.

            Show
            markewaite Mark Waite added a comment - Branch names containing slashes and tag based checkout are both supported since git client plugin 1.10.0 through the commit submitted by Alexander Link. The online help for the "Branches to build" field has been updated to explain the extended syntax. The extended syntax allows the plugin to continue supporting the old format branch specifiers and still allow specification of branch names with embedded slash characters (like develop/my-branch). The extended syntax also allows checkout of tags.
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 144494 ] JNJira + In-Review [ 205913 ]

              People

              • Assignee:
                Unassigned
                Reporter:
                hayafirst Yi Wen
              • Votes:
                4 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: