[JIRA] [jira-plugin] (JENKINS-32087) Configure JIRA credentials at the Job configuration level

8 views
Skip to first unread message

owood@cloudbees.com (JIRA)

unread,
Dec 15, 2015, 3:44:01 PM12/15/15
to jenkinsc...@googlegroups.com
Owen Wood created an issue
 
Jenkins / Improvement JENKINS-32087
Configure JIRA credentials at the Job configuration level
Issue Type: Improvement Improvement
Assignee: Unassigned
Components: jira-plugin
Created: 15/Dec/15 8:43 PM
Priority: Minor Minor
Reporter: Owen Wood

We are providing build management support services to more than 20 divisions like Engineering, Infra, etc. This feature fills up security loop hole, When we provide Jenkins as service we don't allow teams to modify other teams jobs. In it's current form we cannot support JIRA Plugin as a service due to security issues.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

owood@cloudbees.com (JIRA)

unread,
Jan 19, 2016, 10:53:04 PM1/19/16
to jenkinsc...@googlegroups.com
Owen Wood updated an issue
Change By: Owen Wood
Currently JIRA credentials can be configured only at the Jenkins Configuration level and not at the Job configuration level.

{quote}
We are providing build management support services to more than 20 divisions like Engineering, Infra, etc. This feature fills up security loop hole, When we provide Jenkins as service we don't allow teams to modify other teams jobs. In it's current form we cannot support JIRA Plugin as a service due to security issues.

{quote}

valentijnscholten@hotmail.com (JIRA)

unread,
Oct 8, 2016, 6:36:01 AM10/8/16
to jenkinsc...@googlegroups.com
Valentijn Scholten commented on Improvement JENKINS-32087
 
Re: Configure JIRA credentials at the Job configuration level

I agree this would make the plugin more usable for bigger/enterprise environments. We don't want to people to be able to know credentials to view other departments projects/issues.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

valentijnscholten@hotmail.com (JIRA)

unread,
Oct 8, 2016, 6:39:02 AM10/8/16
to jenkinsc...@googlegroups.com
Valentijn Scholten edited a comment on Improvement JENKINS-32087
I agree this would make the plugin more usable for bigger/enterprise environments. We don't want to people to be able to know credentials to view other departments projects/issues.

It could be beneficials to start using the Jenkins Credentials Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin

yanchen.li@outlook.com (JIRA)

unread,
Feb 15, 2017, 10:15:02 AM2/15/17
to jenkinsc...@googlegroups.com
yc li updated an issue
 
Change By: yc li
Priority: Minor Critical

adrien.lecharpentier@gmail.com (JIRA)

unread,
Mar 15, 2019, 3:23:02 AM3/15/19
to jenkinsc...@googlegroups.com
Adrien Lecharpentier commented on Improvement JENKINS-32087
 
Re: Configure JIRA credentials at the Job configuration level

At this moment, the plugin is using credentials-plugin to store the username/password to connect the a Jira server. It was not the case when this ticket was created but only since 3.0.0 (May 20th, 2018).

The thing is, from what I see, the plugin allow to configure Jira connection on the global level only. So that we can maximize the connection details usage. Having the connection details configurable on the job / folder level might go in the opposite direction (not really in the folder case but bear with me).

I didn't see any step / action in the plugin requiring any credentials, as they all JiraSite#get to find the Jira configuration required for project.

I'm not saying we couldn't make this happen, I'm just wondering about the need to have the Jira server connection configurable on job level, as most of the time (all the time?) the connection is configured by an administrator.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

delrocq.mathieu@gmail.com (JIRA)

unread,
Apr 18, 2019, 1:47:03 PM4/18/19
to jenkinsc...@googlegroups.com

Hello, we need it in our company so I will try to do it if it is ok for you. I started somes developments at https://github.com/mat1e/jira-plugin/tree/feature/JENKINS-32087_credentials_at_job_level if you want to take a look.

delrocq.mathieu@gmail.com (JIRA)

unread,
Apr 23, 2019, 12:39:05 PM4/23/19
to jenkinsc...@googlegroups.com

delrocq.mathieu@gmail.com (JIRA)

unread,
Apr 23, 2019, 12:39:05 PM4/23/19
to jenkinsc...@googlegroups.com
Mathieu Delrocq started work on Improvement JENKINS-32087
 
Change By: Mathieu Delrocq
Status: Open In Progress

delrocq.mathieu@gmail.com (JIRA)

unread,
May 2, 2019, 11:03:02 AM5/2/19
to jenkinsc...@googlegroups.com

delrocq.mathieu@gmail.com (JIRA)

unread,
May 3, 2019, 4:44:02 AM5/3/19
to jenkinsc...@googlegroups.com

delrocq.mathieu@gmail.com (JIRA)

unread,
May 21, 2019, 8:24:03 AM5/21/19
to jenkinsc...@googlegroups.com
Mathieu Delrocq assigned an issue to Unassigned
Change By: Mathieu Delrocq
Assignee: Mathieu Delrocq

radek.antoniuk@quiddia.com (JIRA)

unread,
Mar 27, 2020, 1:12:03 PM3/27/20
to jenkinsc...@googlegroups.com
Radek Antoniuk commented on Improvement JENKINS-32087
 
Re: Configure JIRA credentials at the Job configuration level

Since JENKINS-44524 this is configurable on the Folder level, which I think serves the purpose of security and transparency on who has access to what.
Therefore I propose to close this and use folder configuration instead.

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

radek.antoniuk@gmail.com (JIRA)

unread,
Apr 5, 2020, 9:00:04 AM4/5/20
to jenkinsc...@googlegroups.com

If anyone from the watchers have a usecase where a folder-level Jira configuration wouldn't be enough, please describe it here.
If not, I will assume that when folder-level configuration is fixed, we can close this one.

radek.antoniuk@gmail.com (JIRA)

unread,
Apr 5, 2020, 9:01:04 AM4/5/20
to jenkinsc...@googlegroups.com

radek.antoniuk@gmail.com (JIRA)

unread,
Apr 5, 2020, 9:01:04 AM4/5/20
to jenkinsc...@googlegroups.com
Radek Antoniuk stopped work on Improvement JENKINS-32087
 
Change By: Radek Antoniuk
Status: In Progress Open
Reply all
Reply to author
Forward
0 new messages