Hello! I hope you can help me. I tried to connect Jira Cloud and Octopus Deploy Cloud.
I have completed all steps as mentioned here: Jira issue tracking - Octopus Deploy
- Install the Octopus Deploy for Jira plugin in your Jira Cloud instance.
- Configure the Jira extension in Octopus Deploy.
were added: Jira Base URL * Jira Connect App Password. Is Enabled
3.In Octopus Deploy Configure the Release Note Options.
were added: Jira username/password
4.Configure the Octopus plugin in Jira. added: Octopus InstallationID
Release Note Options connection test response : The Jira connection was tested successfully;
,but Jira Connect App Password integration test response: Failed to get authentication token from Jira Connect App.
I can not figure out where is a problem, because configuration process not so complicated.
I can not catch octopus request to Jira.
I tried reinstalled more times Jira Cloud Plugin and Octopus Jira Integration configuration.
Thanks in advance.
Thanks for reaching out and welcome to the Octopus Deploy community! I’m sorry to hear you are having trouble getting Octopus Deploy and JIRA connected, but I’d be happy to help take a closer look.
As an initial step in troubleshooting, I set up my connection to JIRA from scratch so we could compare our configurations. For the JIRA Connect App portion of the setup, you would want to make sure to grab the JIRA Connect App password from the Octopus Deploy app configuration page within JIRA and also supply the Octopus Installation ID as well (this value can be found under
Configuration > Settings > Jira Integration within the Octopus Deploy server UI) :
With your JIRA Connect App password saved and your Octopus Installation ID added, you would want to save this page, so everything is in place when Octopus Deploy attempts to make its initial connection. This has tripped me up before, as if the JIRA configuration page is not saved with this information initially then the integration test from Octopus Deploy will fail.
After saving things here, I would then navigate back to your JIRA integration within Octopus Deploy (
Configuration > Settings > Jira Integration) and test the configuration once more after supplying the proper values (including the JIRA Connect App Password that was saved earlier).
Note that if you don’t have access to the JIRA Connect App password or did not supply the proper Octopus Installation ID when setting up the application then you will need to uninstall and reinstall the Octopus Deploy app from JIRA for this information to display again.
I’ll also link our baseline troubleshooting documentation for this particular feature, in case this helps at all as well.
I hope this initial information helps get you unstuck, but if you are still having trouble could you let me know what versions of Octopus Deploy and JIRA you are currently using so I can dive deeper into this on my side?
Thank your for quick response.
I suppose Octopus Deploy Cloud and Jira Cloud are last version products.
I have reinstalled Octopus Deploy for Jira plugin and update both registration forms of systems. Were copied the jira part - Octopus Installation ID and to Octopus conf. forms - Jira Connect App Password, URL, and etc. I saved both forms before testing. The test connection result is wrong. The same response got.
Failed to get authentication token from Jira Connect App.
Maybe additional configuration required before connect Octopus to Jira. I am new in Octopus , but integration description looks like not complicated.
Thank in advance.
I’m sorry to hear you are still having trouble getting things connected, but thank you for the update.
For my configuration, I did the following:
- Installed the Octopus Deploy application within JIRA, ensuring to save the JIRA Connect App Password and also supplying my Octopus Installation ID. I then saved this page.
- Supplied the necessary values on the JIRA configuration page within Octopus Deploy (
Configuration > Settings > Jira Integration). These values should include
Jira Instance Type (
Cloud in my case)
Jira Base Url (i.e.
Jira Connect App Password (From the Octopus Deploy app in JIRA)
Octopus Installation Id (Should be pre-filled)
Octopus Server Url (If blank, can be set via
Configuration > Nodes in the Octopus Server UI)
Jira Username (Username for JIRA, format should be
Jira Password: This should be a Personal Access Token (PAT) generated from within JIRA.
- I then saved this configuration page and the connection tested successfully.
If you’ve followed our baseline documentation for configuring this integration and are still unable to get things connected then it might be best to jump on a Zoom call and walk through your configuration together, if that works for you.
Let me know if you are still having trouble and if you’d like to jump on a Zoom call and I can get an invite generated. On my side, I typically work from 9:00-5:00 PM MST, so let me know what works best for you and we can coordinate around that. If my working timezone doesn’t line up well with yours I can also work with another member of my team in a different timezone to get something scheduled if needed.
I hope this helps and looking forward to hearing back from you,
Thanks a lot of your support.
I am confusing. It would be great to have your assistance via ZOOM.
Pls schedule a time slot for a call in ZOOM, tomorrow at 1.00 PM MST Time Zone if that is convenient for you.
Please provide the zoom invitation link.
I’ll set up some a new instances for testing.
No worries at all, that works for me!
I just sent out an invite via Google Calendar with a Zoom link included for 1:00 PM MST today, but let me know if you don’t receive anything and I can send the link via a private message as well.
Talk to you soon,
It was a pleasure chatting with you on the phone today.
As discussed, I’ve rescheduled our call for Friday @ 1:00 PM MST so you can get your Zoom permissions set for screensharing. Please let me know if you don’t get the invite, otherwise I look forward to meeting again in a few days.
It was good chatting with you on the phone again on Friday, although I’m sorry we couldn’t get things working as we’d hoped.
As a recap of the call, it seems like something is not working quite right when saving your Octopus values within JIRA (we kept getting an HTTP 400 (Bad Request) on the save operation for Octopus installation ID).
You mentioned this was a fresh instance of JIRA and didn’t contain any historical data, so you would try setting up a new account/instance to see if this allows things to work as expected when saving your Octopus installation ID within JIRA.
Hopefully setting up a new instance of JIRA does the trick, but let me know if you are still having trouble and I’d be glad to assist further.
Thank you for your assistance.
I repeated all of the steps for new Jira and Octopus deployment instances.
Unfortunately, the mistake persisted.
I had a problem with the step save Jira form.
I received a response http 400 error.
Screen short in an attachment.
I’m sorry you are still having trouble with this integration, but thank you for the updates.
As a next step in troubleshooting this, would you be able to upload a HAR file containing the requests made to JIRA when adding the Octopus installation ID?
Here is a secure link where you can upload this capture to, as it could potentially contain sensitive information.
A colleague also sent me this JIRA bug where a 400 error is incorrectly thrown due to rate-limiting, and while I don’t know if this is the issue in your case I figured it wouldn’t hurt to mention it in case you are doing some other testing against this JIRA instance where you might be hitting a JIRA rate limit.
Looking forward to hearing back from you,
Thank you very much for your assistance.
I’ve been doing what you’ve asked.
Har (zasada3.atlassian.net 1.har) has been uploaded.
Please let me know if there is anything else that needs to be done.
Thank you for uploading the HAR file!
In taking a look, I may have spotted the issue. I compared your POST request to mine, and noticed that while I connect to the Octopus endpoint
https://jiraconnectapp.octopus.com/octopus/setup over TCP port 443, your HAR file shows that you are somehow hitting this endpoint over TCP port 80:
My request (note the
:443 appended to the remote address):
Your request (same endpoint and remote address, but over TCP port 80):
Is it possible that there are any networking devices such as a proxy sitting between you and the Octopus Deploy endpoint that might be interfering with your network traffic?
One quick way to test this would be to jump on another network to see if this behavior persists when you try to save the Octopus Installation ID within JIRA.
Hopefully this helps shed some light on what’s happening, but feel free to reach out again if this doesn’t help get things unstuck.
I have repeated all stages of integration from other network in different environment. Unfortunately, the problem remains the same.
Har file (zasada3.atlassian.net_3.har) was uploaded.
Please have a quick review it.
Thank you for the update, and also for uploading the new HAR file.
In taking a look, it seems like the same issue is occurring, which is strange given that you switched to a different networking environment for this latest test.
As a next step, I’m wondering if you can get things connected by crafting your own request and posting this to the Octopus Deploy JIRA endpoint (
I will share a screenshot of how I did this on my side for your reference using an API browser extension (you could also perform this action via the CLI using curl or another similar tool):
So in this case, you’ll need to send a POST request to the endpoint
https://jiraconnectapp.octopus.com/octopus/setup containing a payload with the content type of
application/x-www-form-urlencoded. The key/value pairs that will need to be passed in the body of the request are
octopusInstallationId, and you should be able to grab these from your browser’s web inspector (similar to how we did this on the call the other day):
This POST request should return with an HTTP 302 (Found) status code, and then if you reload JIRA you should see that the installation ID has been populated as expected, which should let you finish your configuration steps within Octopus Deploy.
Let me know if you have any trouble with the steps I discussed above and I’d be happy to jump on a call to work through this more together.
Hopefully this gets things unstuck, but let me know how it goes in your testing.
Thanks for your response.
I am a little bit confusing regards appropriate values for
baseUrl , and
Just to clarify. Which values are correct? I mean field mapping.
Octopus Deploy configuration form in Jira has three field.
There are Jira Base URL,Jira Connect App Password
,Octopus Installation ID.
Thank you for reaching back out.
In taking a look at your screenshot, it looks like you are using the
form-data content type, but you’d instead want to use
This should let you enter the key/value pairs as I did in the screenshot from my previous message, which you can get by inspecting the bad JIRA request in your browser and navigating to the
payload tab (the second screenshot in my previous post).
Hopefully that gets things working, but if it doesn’t I should be available to meet tomorrow if you’d like to jump on a call. On my side, I am available from 9:30-10:30 AM MST, or from 2:00-3:00 PM MST. Let me know if you’d like to meet up over Zoom and I will get a calendar invite sent out, or we can try to find another time next week if that would work better on your side.
It would be great to speak with you today.
Pls schedule a time slot for a call in ZOOM, for today at 2.00 PM MST Time Zone if that is convenient for you.
Please provide the zoom invitation link.
Perfect, that sounds great!
I just sent out a Zoom invite via Google Calendar for 2:00 PM MST today, but let me know if you didn’t receive it and I can send you the link via a private message as well.
Talk to you soon,
Thanks for taking the time to meet with me last week, and I hope you had a good weekend!
I wanted to reach out as I made some progress on this, and I think we are now on the path toward resolving the underlying problem.
In doing some digging on my side, I was able to track back the requests you’ve been making from JIRA and it looks like we are not properly matching the installation ID value you are passing. I’m reasonably sure you are passing the correct value for this as we’ve done a few tests now (), so I’ve re-escalated your case to our engineering team with this new information so they can dive deeper into this.
I’m sorry this took so long to diagnose, but I’m glad I could finally find a good lead to follow up on.
I will reach back out as soon as I have an update, but let me know if I can be of any other help in the meantime.
Thank you very much for your assistance and support.
I’ll wait for your update.