Open eskaarup opened 5 years ago
I'd like to get the answer as well for this question... seems kind of strange to release a azure devops integration that doesn't support its own repos
This is related to issue #7, describing the same behavior for BitBucket.
I am also curious to know about Azure Repos.
Based on the responses to the reviews on Jira it's not supported, which is very disappointing,
Currently there is no official way to link commits in Azure DevOps Git Repo with Jira issues. You can however use third party plugins for that.
Yeah, this needs to be supported. I'm not interested in being forced to use three services when I originally came trying to work with two.
I just spent a bunch of time troubleshooting this issue -- everything appears to be setup fine, no errors, but there's "No work items" listed on the release and no info appearing in JIRA. Just to come on here and find out that they don't support their own repo host? Ridiculous.
@rogersmj it's pretty clear this integration is not ready for release. Issues all over the place and no support for their own repo.
is there any tentative date for this to be even take this into account? would love to have it for azure repos or any way we can contribute?
I don't work for Microsoft, but Azure repo support seems to be in the work according to the App:
Support for Azure Repos would be added in the next iteration (in roughly 2-3 weeks).
https://marketplace.atlassian.com/apps/1220515/azure-pipelines-for-jira?hosting=cloud&tab=versions
Although that is good news, we're already 5 weeks in. This tool is useless for us unless Azure Repos are supported.
6 weeks later... We still really want this feature. Up to 8 weeks now, but at least there is an update from Azure Devops:
Azure Repos support required changes on both sides of the integration. We follow a ring wise deployment model. The support is being deployed ring by ring. We should be done with all rings by 9/1. Depending on the ring your Azure DevOps org belongs to, you'll see the support come alive between now and 9/1
Source: https://marketplace.atlassian.com/apps/1220515/azure-pipelines-for-jira?hosting=cloud&tab=reviews
Sooo.... It's looking pretty grim here if you don't want to pay for another 3rd party add-on to use this with AzureDevops. The only functionality that I'm seeing it offering is it will list links to Jira work items when the commits for a release include a Jira work item key when you make a release in AzureDevops. The documentation even has two paid third party plugins having at least one installed as prerequisites to get the full functionality out of this. Link
After linking and creating a release, this is the only functionality that I got:
It just added a couple links to work items from the last CI release. If you compare it to older releases, it will compare the commits in-between as well. We are using a YAML pipeline, so it seems to work ok, but isn't really what we we were hoping out of this integration. We were hoping for more of what the paid add-ons provide as a free integration from Microsoft.
It hasn't updated the ticket statuses though. It may have to be a release created after the integration in order for it to do that, but I kind of doubt that. I still think it requires a paid add-on.
Update: Just a warning that commit messages for containing Jira issue keys are case sensitive. You must use ABC123 and abc123 will not get picked up. New issue opened here: #14
Also: Whatever smart commit identifier is being used to identify work items in a release should also be used in places like PRs and builds. So when a PR is made we can see if a work item is attached and potentially enforce an attached work item policy even if we are using Jira to track work items.
Sooo.... It's looking pretty grim here if you don't want to pay for another 3rd party add-on to use this with AzureDevops. The only functionality that I'm seeing it offering is it will list links to Jira work items when the commits for a release include a Jira work item key when you make a release in AzureDevops. The documentation even has two paid third party plugins having at least one installed as prerequisites to get the full functionality out of this. Link
This was definitively a disappointment to me. I had expected this integration to be capable of at least showing PR information in JIRA on issues. In hindsight I see that the name "Azure Pipelines for JIRA" gives it a bit away that we should not have expected full Azure Repos support in JIRA.
Hopefully Atlassian and Microsoft Azure DevOps will continue with their cooperation now and create official support for Azure Repos in Atlassian JIRA too.
The app documentation says it supports Azure Repos as well but I could not get it to work. Any help is appreciated if I needed to change some config or others as such.
@apoorvakrishna66 at another link one of MS guys informs us that v1.0.9 - This version adds the support for Azure Repos to the plugin. is a misunderstanding. It is still needed to install paid, third party plugins in from Jira marketplace...
Hi there, I have the same issue, at work, we are using Azure Repos and Jira, but can't get git integrations until and unless I use the paid version. Did you guys find a workaround or is there any update from Microsoft regarding this?
Any news?
Has there been any update on this? I would love to have these integrations.
Any news on this?
Just adding a plus-one -- our organization would like this too.
I have tried to get this up running within our organization, but it is not clear for me if this integration only supports GitHub and not Azure Devops GIT.
Do we need to install another 3'party app in Jira to get GIT connectivity or is this an error ?
As a side question... will it only update the tickets when all stages has been completed ?