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)
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.