Azure DevOps(formerly VSTS) Work Item links do not work when work items in different project #3622
Labels
integration-azure
Issues or features related to Azure DevOps integrations
triage
Needs to be looked at
Description
As seen in the screenshot below, I get good detection of Azure DevOps links in the PR commit messages.
When pressing on the links, the Pull Request link is fine, and looks like so:
https://dev.azure.com/<ORG_NAME>/<PROJECT_NAME1>/_git/<REPO_NAME>/pullrequest/6123456
However, the Work Item link does not work, and takes me to a 404 site.
It looks like this:
https://dev.azure.com/<ORG_NAME>/<PROJECT_NAME1>/<REPO_NAME>/_workitems/edit/4123456
This is due to two things.
The repository name cannot be used here. In order to make it work, the "<REPO_NAME>/" needs to be removed, so instead of "https://dev.azure.com/<ORG_NAME>/<PROJECT_NAME1>/<REPO_NAME>/_workitems/edit/4123456", the final url will be "https://dev.azure.com/<ORG_NAME>/<PROJECT_NAME2>/_workitems/edit/4123456"
The Work Item exists in a different project. The real address is "https://dev.azure.com/<ORG_NAME>/<PROJECT_NAME2>/_workitems/edit/4123456"
However, it doesn't matter that it says <PROJECT_NAME2>. When I type "https://dev.azure.com/<ORG_NAME>/_workitems/edit/4123456", I get redirected to the correct destination in the correct project like so: "https://dev.azure.com/<ORG_NAME>/<PROJECT_NAME2>/_workitems/edit/4123456"
Not everyone has this setup, but this is how my organization choose to use it.
I'd just like to report it, it is a small issue and not something that is urgent to fix, but it annoyed me and I could not see any existing bug on this.
GitLens Version
v15.5.1
VS Code Version
Version: 1.93.1 (user setup)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
Git Version
git version 2.34.1
Logs, Screenshots, Screen Captures, etc
Pressing on the Work Item:
The text was updated successfully, but these errors were encountered: