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

Allow folder scope credential for Jira connection

    Details

    • Similar Issues:

      Description

      We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

      This connection must be specific to the project and not visible to others

       

      That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

      Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

       

      It should look like this :

        Attachments

          Activity

          matttt Mathieu Delrocq created issue -
          matttt Mathieu Delrocq made changes -
          Field Original Value New Value
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection with a credential wich will not be visible for others projects.

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like something like :

          !image-2019-04-15-18-00-36-370.png|width=592,height=108!
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection with a credential wich will not be visible for others projects.

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !image-2019-04-15-18-00-36-370.png|width=592,height=108!
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection with a credential wich will not be visible for others projects.

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !image-2019-04-15-18-00-36-370.png|width=592,height=108!
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others


           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !image-2019-04-15-18-00-36-370.png|width=592,height=108!
          matttt Mathieu Delrocq made changes -
          Summary Allow project/folder credential for Jira connection Allow folder scope credential for Jira connection
          matttt Mathieu Delrocq made changes -
          Link This issue duplicates JENKINS-32087 [ JENKINS-32087 ]
          matttt Mathieu Delrocq made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Duplicate [ 3 ]
          Hide
          malice00 Roland Asmann added a comment -

          This issue is definitely NOT a duplicate of JENKINS-32087, since it is about using a different type of credential and JENKINS-32087 is about setting the credential at job-level!

          Since I am also really interested in using folder-level credentials to login to JIRA, I took the liberty of reopening this issue.

          Show
          malice00 Roland Asmann added a comment - This issue is definitely NOT a duplicate of JENKINS-32087 , since it is about using a different type of credential and JENKINS-32087 is about setting the credential at job-level! Since I am also really interested in using folder-level credentials to login to JIRA, I took the liberty of reopening this issue.
          malice00 Roland Asmann made changes -
          Resolution Duplicate [ 3 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          malice00 Roland Asmann made changes -
          Link This issue duplicates JENKINS-32087 [ JENKINS-32087 ]
          matttt Mathieu Delrocq made changes -
          Assignee Mathieu Delrocq [ matttt ]
          matttt Mathieu Delrocq made changes -
          Status Reopened [ 4 ] Open [ 1 ]
          matttt Mathieu Delrocq made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          matttt Mathieu Delrocq made changes -
          Attachment jira_plugin_folder_credential.png [ 46961 ]
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others


           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !image-2019-04-15-18-00-36-370.png|width=592,height=108!
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

           
          matttt Mathieu Delrocq made changes -
          Attachment image-2019-04-15-18-00-36-370.png [ 46725 ]
          matttt Mathieu Delrocq made changes -
          Attachment jira_plugin_folder_credential.png [ 46962 ]
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

           
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

           

           

           
          matttt Mathieu Delrocq made changes -
          Attachment jira_plugin_folder_credential.png [ 46962 ]
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

           

           

           
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !jira_plugin_folder_credential.png|width=288,height=128,thumbnail!

           

           

           
          matttt Mathieu Delrocq made changes -
          Attachment jira_plugin_folder_credential.png [ 46961 ]
          matttt Mathieu Delrocq made changes -
          Attachment jira_plugin_folder_credential.png [ 46963 ]
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !jira_plugin_folder_credential.png|width=288,height=128,thumbnail!

           

           

           
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !jira_plugin_folder_credential.png|width=566,height=254!

           

           

           
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !jira_plugin_folder_credential.png|width=566,height=254!

           

           

           
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !jira_plugin_folder_credential.png!

           

           

           
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !jira_plugin_folder_credential.png!

           

           

           
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

           

           
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

           

           
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !image-2019-04-15-18-00-36-370.png|width=592,height=108!
          matttt Mathieu Delrocq made changes -
          Attachment jira_plugin_folder_credential.png [ 46963 ]
          matttt Mathieu Delrocq made changes -
          matttt Mathieu Delrocq made changes -
          Description We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !image-2019-04-15-18-00-36-370.png|width=592,height=108!
          We have multiple projects on Jenkins and we would like to let the projects owners configure their own Jira connection.

          This connection must be specific to the project and not visible to others

           

          That is why we want to add the possibility to set a Folder scope credential in the job configuration to override the global one.

          Accordingly to this function, the Jira connection must be visible on the job even if there is only one configured in the Global Configuration.

           

          It should look like this :

          !Jira_screen_concept_folder_credential.PNG|width=664,height=121!
          Hide
          matttt Mathieu Delrocq added a comment -

          A pull request was opened for this issue : https://github.com/jenkinsci/jira-plugin/pull/188.

          Show
          matttt Mathieu Delrocq added a comment - A pull request was opened for this issue : https://github.com/jenkinsci/jira-plugin/pull/188.
          matttt Mathieu Delrocq made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          Hide
          malice00 Roland Asmann added a comment -

          So... 3 months have passed since the pull request... Any news on this?

          Show
          malice00 Roland Asmann added a comment - So... 3 months have passed since the pull request... Any news on this?
          Hide
          matttt Mathieu Delrocq added a comment - - edited

          The PR is still in review and I don't have much times to work on it for the moment... I will continu as soon as possible.

          And I will need to rework my solution to keep binary compatibility.

          I hope to work on it next month.

          Show
          matttt Mathieu Delrocq added a comment - - edited The PR is still in review and I don't have much times to work on it for the moment... I will continu as soon as possible. And I will need to rework my solution to keep binary compatibility. I hope to work on it next month.

            People

            • Assignee:
              matttt Mathieu Delrocq
              Reporter:
              matttt Mathieu Delrocq
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: