Jira Issue Tracker setup issues

[zandreb]

Hi
I’ve installed the Octopus Deploy tool for JIRA on JIRA. I’m struggling to configure it though. Everywhere is mentioned the Configuration - Settings section on the Octopus web portal. But I’m not seeing those sections.

[jeremy.miller]

Hi @zandreb,

Thanks for reaching out.

I’ve taken a screenshot of the buttons required to get there:

Can you please let me know if it looks like that on your end or what you’re seeing?

Best,
Jeremy

[zandreb]

Nope
I’m assuming it either has to do with user permissions, or I need and upgraded account of Octopus?

[jeremy.miller]

Hey @zandreb,

Thanks for the screenshot. Yeah I think this comes down to permissions. Can you please reach out to your Octopus Admin and either have them do the setup or give you the proper permissions?

Please let me know how it goes.

Best,
Jeremy

[zandreb]

Hi @jeremy.miller
I was able to get the correct permissions and am currently running my first build & deploy with the new app installed. Thanx for the assist

[jeremy.miller]

Hey @zandreb,

You’re very welcome! Thanks for updating me.

Please let us know if you run into any other issues going forward.

I hope you have a great weekend.

Best,
Jeremy

[zandreb]

Hi Jeremy
So far as I can see I’ve now completed the setup. I can test in Octopus (Configuration->Settings->JIRA Integration) both the JIRA App Pw and the Release Notes Options test successfully integrate with the details I entered.
In Azure DevOps I’ve also included a step called Push Package Build Information to Octopus so that Octopus can receive the commit info from the Azure pipeline.
After this, I created a ticket in JIRA, added a few commits with the relevant key (IPD-7856), and kicked off a build (AzureDevops), and deploy afterward (Octopus). However, I’m not seeing any changes in either Octopus (where I expected to see release notes) or JIRA (where I expected to see new deployment info on my ticket)

[Kenneth_Bates]

Hi @zandreb,

Thanks for keeping in touch! I’ll jump in for Jeremy as he’s currently away on holiday.

My first thought is in regards to the ordering of these steps in your ADO process. Is your Push Package Build Information step configured to run before your Create Octopus Release step? This ordering is important (build info pushed before the release is created).

If that checks out, do you see any build information against the specific package (in the Octopus UI under Library > Package) or this specific project release? What you see in both those places might give us a clue as to what might be causing this unexpected behavior.

I look forward to hearing back and getting to the bottom of this one!

Best regards,

Kenny

[zandreb]

Hi @Kenneth_Bates

On this first one, I never had a step in my pipeline called Create Octopus Release. I’ve added one now and will see what happens when I run a build on that pipeline. It seems as though we do not push packages at all to Octopus, but rather publish them to the ADO Artifacts. Will this be an issue?

On the second one, I do not currently see any packages at all in Octopus which I can query. Probably for the reason mentioned above

[Kenneth_Bates]

Hi @zandreb,

Thanks for following up! That should be fine, the key important thing to point out is that the build information just has to be pushed before the release is created, as it’s snapshotted into the release.

Do you see any this info in the web portal under Library > Build Information against the specific package? Or is the issue that it’s not populating in the release itself? Would you be willing to send a screenshot showing what you see, and also the release notes template you have configured on the project (in your project’s Deployments > Settings in Release Notes Template)?

I look forward to getting to the bottom of this one!

Best regards,

Kenny

[zandreb]

Hi @Kenneth_Bates you ready for some serious screenshot spam?

I’ve never noticed this tab before but I do see some of our JIRA ticket references under the Library -> Build Info

For now, I’ve only included 2 packages (app called Admin) where I want to test instead of all 20 we have.

If I click into the bottom one and then into a build where I know there was commits I find this

So something is working, just not sure which part yet. I might also add only 1 ticket would have had a commit in the Admin package, the other 2 tickets are unrelated.

I still have nothing under Library -> Packages
I’ve unfortunately deleted the release created after I added the step Create Octopus Release so I cannot share screenshots, but I viewed deleted the release packages and they did not have this kind of build info included as mentioned in the documentation. Although this might just be because I never actually committed anything new for that test build, I just ran the ADO pipeline to see what the new step does.

I do not currently have a release notes template set up

[Kenneth_Bates]

Hi @zandreb,

Thanks for keeping in touch and for that extra information! (I love screenshot spam! )

Is the issue that you’re not seeing these work items listed in the release notes? If you use the example release notes template, that should then grab the work items associated with each package, and populate the release notes with it. E.g.

Here are the notes for the packages
#{each package in Octopus.Release.Package}
- #{package.PackageId} #{package.Version}
#{each workItem in package.WorkItems}
    - [#{workItem.Id}](#{workItem.LinkUrl}) - #{workItem.Description}
#{/each}
#{/each}

Also just to rule it out, I believe the information you’ve provided implies the Azure DevOps Issue Tracker extension in Octopus has been configured and enabled (Configuration > Settings > Azure DevOps Issue Tracker) but could you confirm that?

Azure DevOps work item tracking integration - Octopus Deploy

Please let me know how you go or if you have any other questions or concerns at all.

Best regards,

Kenny

[zandreb]

HI @Kenneth_Bates
Sorry for the slow response

I’ve included the release notes section as per your instructions, but it still does not populate the actual release.

However, I can see in the Library -> Build Info -> the relevant Work items with their link to my JIRA tickets. So the info is there. I see this when I click on the version url of the package

Not sure what this is about when I click on the actual package ID

My Azure DevOps Issue Tracker has not been enabled. To be honest, I’ve been focused on getting the JIRA-Octo part working, and I assumed that since I can see my Work Items in the Library -> Build Information that the ADO-Octo part is working. Do I need to enable Azure Devops Issue Tracker?

[jeremy.miller]

Hey @zandreb,

It looks like you may be experiencing one of our current Jira bugs with this.

It looks to be this one: https://github.com/OctopusDeploy/JiraIntegration/issues/56

Could you please confirm this looks to be the same issue you’re experiencing?

Best,
Jeremy

[zandreb]

@jeremy.miller yeah looks like the same issue. There are a few variables in the error messages that’s different obviously, but by all accounts it looks like the same issue

[jeremy.miller]

Hi @zandreb,

Thanks for confirming. This is one of our integrations teams’ top priorities right now so if you subscribe to that, you should get updates ASAP.

Please let me know if you have any other questions in the meantime.

Best,
Jeremy