-
Notifications
You must be signed in to change notification settings - Fork 19
Description
Severity
Not blocking customers, the deployment still works and work items still show correctly on all other pages.
Version
2025.4.10395, also seems to be present in 2024.4
Latest Version
I could reproduce the problem in the latest build
What happened?
If I have build information work items linked from ADO (using ADO Boards - Work Items) and push a package to Octopus with build information in it from an ADO project with a space in it, the work items will show fine in the package area in Octopus for that uploaded package. It will also show fine in the release itself.
However, when going to deploy the release, the Changes tab shows the work items in a broken state where the URL seems to see the space as a break in the URL.
This does happen in a 2024.4 version but it manifests slightly differently. Below is how it displays in 2025.4.10395 (on the left) and 2024.4.7147 (on the right). This is from the same ADO project called:
Nuget - Random Quotes Push to OctoDC (On-Prem) - V5
Both links send you to a 404 not found ADO page so both dont work to show the work items.
I have also tested this on an ADO project called Test_Space which did display correctly and allows me to access the work item from the link (this is in 2025.4.10395).
As mentioned, all other pages show the Build information Work Items correctly ie the package itself:
And the build information work items in the deployment:
So this just seems to affect the Changes Tab within a deployment.
Reproduction
- Have an ADO issue tracker connection setup in Octopus.
- Ensure you have an Octopus Project setup with the package you are going to be using for testing (
Deploy a PackageStep is fine). - Ensure you have a Github or other provider repository with your code in.
- Have an ADO project set up with a space in its name to build a package from that repository and push it to Octopus with Build information. You will also need it to create a release in Octopus and deploy that release.
- Have the ADO project settings
Boardssection link to your GitHub (or other providers) repository with your package code in. - Create a commit on your code in the package repository with a commit message.
- Create an ADO Board Work Item, link it to that commit.
- Run the pipeline in ADO and look at the release deployment in Octopus, you will see the
Build Informationtab show the Work Item correctly and link to it. However, theChangestab will show the URL separated and the link wont work.
Error and Stacktrace
N/AMore Information
Initial customer ticket (Internal) - https://octopuscd.zendesk.com/agent/tickets/189576
RnD (Internal) - https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1771247212287379
Workaround
There is no current workaround for this other than to re-create your ADO project without a space in its name.
However, this only affects the changes tab in the deployment, so you can access the work item from the Build Information tab in the deployment and also from the package itself or the release.