Unable to link jira and jenkins
Asked by Tyler Gale:

After creating credentials as stated in this page.

<https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-jenkins/> the credentials are not able to be selected.

Is this a bug or is my process incorrect.


Answers:
author: Tyler Gale
body: After gathering the needed connection info from the Jira Cloud instance and creating a credential for the secret text to be used in the jira extension/plugin found in the jenkins GUI, I am looking to select the newly created credentials and they seem to be missing from the system as if they were not created. When investigating by going into the credentials menu the newly created credentials are present just not able to be assigned to the jira integration portion of the System configuration menu.

![Screenshot from 2024-08-12 14-56-09.png](https://community.atlassian.com/t5/image/serverpage/image-id/341340i1CF17CDCFB631CBF/image-size/large?v=v2&px=999 "Screenshot from 2024-08-12 14-56-09.png")

comments: author: Tyler Gale
body: ![Screenshot from 2024-08-12 14-57-56.png](https://community.atlassian.com/t5/image/serverpage/image-id/341344i72714A4F8ECC26C9/image-size/large?v=v2&px=999 "Screenshot from 2024-08-12 14-57-56.png")


author: Trudy Claspill
body: Hello [@Tyler Gale](/t5/user/viewprofilepage/user-id/5315908)

Welcome to the Atlassian community.

Exactly which steps in that page did you follow to create credentials?

Which step are you at now, and how is what you're seeing different than what you think you should be seeing?

comments: author: Trudy Claspill
body: As per this section of the document, within Jira you should get a webhook and secret token.

![Screenshot 2024-08-09 at 3.30.30?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/341070i2F6EAC3CDF6FC6E7/image-size/large?v=v2&px=999 "Screenshot 2024-08-09 at 3.30.30?PM.png")

You need to provide that information (copy it into) a screen in Jenkins:

![Screenshot 2024-08-09 at 3.31.56?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/341071i77E4960B91CD4C75/image-size/large?v=v2&px=999 "Screenshot 2024-08-09 at 3.31.56?PM.png")


author: Trudy Claspill
body: Note that I don't actually have a Jenkins environment where I can try this myself.

The dropdown you mentioned does not appear to be included in the instructions from the referenced document. Here is a screen image of the instructions for completing the connection on the Jenkins side.

If I am overlooking the step you are trying to execute, please point out to me which step in the documentation corresponds to what you are trying to do, and confirm you have completed the prerequisite steps.

![Screenshot 2024-08-12 at 12.02.49?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/341345iE8173A31D076CB56/image-size/large?v=v2&px=999 "Screenshot 2024-08-12 at 12.02.49?PM.png")


author: Tyler Gale
body: In step 5 you need to create a credential to store the secret key as text. This is the place I am unable to select an already created credential for use with this plug in.


author: Trudy Claspill
body: So is it 5.f. that is the trouble spot? It mentions using the **Secret** dropdown, and I see in the screen you shared a dropdown labeled **Credentials** . Have you tried starting to type in the name of the credentials that you created; i.e. **jira**?


author: Tyler Gale
body: Nothing happens when typing.


author: Trudy Claspill
body: Is there a **Secrets** dropdown on that screen?

Which version of the **Atlassian Jira Software Cloud**plugin did you install on your Jenkins system?

What version of Jenkins are you using?

Given that I don't have access to a Jenkins system of my own to test this out, my ability to help you debug is going to be limited. The first question I would be trying to address is why your screen has a **Credentials** dropdown instead of a **Secrets** dropdown. Maybe that is due to the plugin version or the Jenkins version.

From the documentation page for the plugin:

<https://plugins.jenkins.io/atlassian-jira-software-cloud/>

I found a link to issue tracking for the plugin:

<https://issues.jenkins.io/issues/?jql=resolution%20is%20EMPTY%20and%20component%3D25523>

Refining the resultant search I found an unresolved bug from 2022 that seems to be describing the same experience as you.

<https://issues.jenkins.io/browse/JENKINS-69744>


Tags: cloud

jira-cloud