@keon94 I think we need to collect AzDo tickes/issues data for those metrics to work. Would you like to work on it? Thanks.

@KlemenDanfoss Hi, the Azure Devops plugin is written in Python, I would like to ask if you are interested in contributing such a feature? @keon94 could help if you have any questions.

@KlemenDanfoss Hi, the Azure Devops plugin is written in Python, I would like to ask if you are interested in contributing such a feature? @keon94 could help if you have any questions.

Sorry, probably can't help with a PR

Alright, let's collect votes first. cc. @keon94

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

Anything new here?

@KlemenDanfoss No progress yet. You can try to share it with the Slack community and see if anyone is interested in it. Azure DevOps is implemented with Python btw.

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

Any thing new here? Is this really a feature that doesn't make sense?

Hi @KlemenDanfoss , as a feature it makes sense. However, we don't have the bandwidth to do this recently.

We would need this feature as well. Especially the Change Failure Rate can't be only calculated based on Health Checks or Automated Post Deployment Tests. Sometimes there are bugs which are not covered by this automated tests and a Bug is then created.

• Is it possible to manually mark a deployment as a failure?
• Probably the same code which exists for gitlab or other providers can be used, just the fetching of the items needs to be adapted based on Azure Devops REST Apis?

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

Any chance we can reopen this? If given directions, I can submit a PR for this.

@slaterx This issue is reopened.
There are two implementations about AzureDevOps in DevLake so far, but they both don't collect incidents.
I think it is similar to jira.
step1: issues in Azure DevOps' board should be collected
step2: make a rule about how to regard issues as incidents. (I think @Startrekzky can help.)
step3: Update dora and AzureDevOps dashboard if neccessary.

cc @klesh

Hi @d4x1, I've reviewed the repo and found out that we have two plugins - one in python and another one in go.

Based on the comment here, the Go plugin skips disabled git repos, but in Azure DevOps, it is a valid use case to have disabled repos hosting work items. I would like some guidance to understand if I can remove this skip in the Go repo, otherwise, I'll attempt the implementation in the python plugin.

The reason for my question is because we have migrated from Azure DevOps to GitHub, however the issues are still collected in the disabled Azure DevOps repos. Keen to hear your thoughts.

cc @klesh

@slaterx Your use case sounds reasonable to me. @mr-ks I think we should allow adding disabled repos in case like this.

Once #7809 is merged, just tweak the query in grafana to obtain all bug type work items from Azure DevOps.

@mr-ks Would you like to take a look at the implementation? Thanks in advance.

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

PR still open...

There was a discussion on the data scope definition of Azure Boards in our Slack community at: https://devlake-io.slack.com/archives/C03APJ20VM4/p1726117905373619?thread_ts=1725410497.368769&cid=C03APJ20VM4

Hello there, are there any updates on this? The PR seems to be open since 3~ months now.

Thanks!