Data Migration from azure devops serveer to new one
I have a problem in data migration from Azure DevOps server to the new one in my case, i have a split database on a different machine. So, I have two environments: each one contains a devops server and database in splitter machines i want to migrate the whole data from different tools to a new one and the problem is as the organization roles i do not have all administration privileges on databases and devops machines So, I want a determined way to get the whole data from the old one to the new one (especially privileges that are required to ask the admin to give me ) with clear steps
Post-job: Cache fails
In the pic above Iam trying to cache my yaml.lock file to reduce runtime and Iam using the azure devops docs to do that. The first Cache step seems to work fine and there is "a cache miss" and then it runs yarn install. But the Error comes in the Post-job: Its taking 10 minutes and then timing out i think. --Note-- Iam using a self hosted agent here and i added GNU Tar and 7-zip and restarted the agent. --End Note-- I dont know if the above had something to do with my problem. But it didnt work before or after. Can anyone help out here?
Error Unauthorized when trigger a flow with Webhook and HTTP request
Hi guys, I have an error when O want to send a webhook from Azure DevOps to trigger a Flow with an HTTP request. In Azure DevOps I get an Unauthorized error. But when I access the HTTP request URL in the browser everything works fine. Can anybody help? Thx!!
Velocity Chart Not Showing Planned Work (Blue Bar) for Specific Sprints
I researched a lot and discussed with my friends as well on this issue but could not get any help. The Velocity Chart widget is not showing planned work (Blue Bar) for first 3 sprints. Earlier it was showing but suddenly it stopped showing. I am unable to find the reason. However from sprint 4 (current sprint) it is showing the planned work. Any help would be appreciated. Here is the snapshot of Velocity Chart configurationAzure DevOps pipeline Jira integration
We are facing an issue on Azure DevOps pipeline integration with jira cloud. When we enable the "Report deployment status to jira" checkbox by choosing the jira service connection and after clicking on the save button, it is getting disabled by itself. There is no error popping up to troubleshoot this issue further. We have service connection in Azure DevOps through Azure pipelines forjira app.Device In Azure AD showing as not compliant, yet in Intune the device is fine and compliant
Hello All I have several devices that are now failing SSO logins because of Conditional Access retuning as the device is not Compliant, Checking the device in Azure AD (Entra) is clearly shows the device is not compliant, which explains why the SSO logins are blocked. But when I check the device in Intune (Endpoint) it shows the device is compliant and all good (you will have to take my word the 2 screen shots are the same device as the host name is blurred) When checking the device ID in Azure AD and Intune they all match as you would expect. The Devices are checking in and Syncing with Azure and Intune on a regular basis. Azure is just not updating with the correct Compliance status from Intune. Any Ideas what is happening Cheers Colin
Has anyone implemented the DORA metrics on top of Azure Devops Services?
We use Azure DevOps Server 2020 on-prem. Specifically, Azure Git Repos and Azure Pipelines. Now we would like to collect the DORA metrics, but first would like to check if anyone using Azure DevOps has done it already. Maybe there is an extension that helps implement it. Maybe 3rd party integration. In general, sharing your experience with DORA metrics and Azure DevOps may be very valuable. Thank you.How to Sync Area and Iteration Paths Between Jira and Azure DevOps
Azure DevOps area and iteration paths do not have a direct replica on the Jira side. So to sync information between both systems, the area and iteration path data has to be mapped to a custom field in the Jira issue. For this to work, you need a customizable AI-powered integration solution like Exalate. This solution will help you generate the script for mapping paths and maintaining the relationships between the work item and the issue. What is an Area Path? An area path establishes a hierarchy for work items related to a specific project. It helps you group work items based on team, product, or feature. Organizations working on a product or feature can use area paths to establish a hierarchy between teams at every level of involvement. You can assign the same area path to multiple teams. What is an Iteration Path? An iteration path assigns work items at the project level based on time-related intervals. Teams can share them to keep track of ongoing projects, specifically for sprints, releases, and subreleases. When new work items are added to the Sprint backlog, they become accessible via the existing iteration path. You can add up to 300 iteration paths per team. Sync Area and Iteration Paths: Jira to Azure DevOps Use Case You can create a custom field in your Jira instance to reflect the data from the iteration and area paths. How does this help your organization? Syncing this data gives more context about the teams involved on the Azure DevOps side. It provides context about the timelines and stages of progress for the mapped projects and entities. Primary Requirements Obtaining the right information from the API on both sides. Writing or generating the correct sync rules for both the incoming and outgoing data. Creating triggers to update the custom fields on Jira automatically. Fetching the right string from the area or iteration path. How Exalate Handles Jira to Azure DevOps Syncs Exalate supports one-way and two-way integration between Jira and Azure DevOps as well as with Zendesk, ServiceNow, Salesforce, GitHub, etc. Exalate also supports AI-powered Groovy scripting with the help of a chatbot. Users can also create trigger-based integrations for real-time syncs and bulk operations. To use Exalate, first install it on both Jira and Azure DevOps. Since this use case requires scripting, you need to set up a connection in the Script Mode. To configure the sync, open Exalate in your Azure DevOps dashboard, go to the connection you want to edit and click on the “Edit connection” icon. You have two options: Outgoing sync (on the Azure DevOps side) refers to the data being sent over to Jira. Incoming sync (on the Jira side) refers to the data to be received from the work item on Azure DevOps. Outgoing Sync (Azure DevOps): Send Area and Iteration Path Details from Azure DevOps to Jira To send out the area and iteration paths from the Azure DevOps work item, use the code below: replica.areaPath = workItem.areaPath replica.iterationPath = workItem.iterationPath The replica retrieves the values of the area and iteration paths from the work item and saves them as a string. On the remote side, you can store the area/iteration path in a custom field using a type string or select list. Incoming Sync (Jira): Set Area Path from Azure DevOps as a Custom Field in Jira Let’s start with the area path. The area path starts with the name of the project. For example, an Azure DevOps project called AzureProject handled by Exalate’s dev team could have an area path: AzureProject\\ExalateDev. To set the area path based on the value received from the remote side text field, use the code below: issue.customFields."Area Path".value = replica.areaPath The issue.customFields."area-path".value retrieves data from the work item and stores it in the designated custom field on Jira. Incoming Sync (Jira) Set Iteration Path from Azure DevOps as a Custom Field in Jira The iteration path shows the name of the project as well as the specific sprint. For example, an Azure DevOps project called AzureProject in the first sprint could have an area path: AzureProject//Sprint1 If you don’t set the value for the Area field in the Sync Rules, Exalate uses the default area that has the same name as the project. To set the iteration path based on the value received from the remote side text field, use the code below: issue.customFields."iPath".value = replica.iterationPath The issue.customFields."iPath".value retrieves data from the work item and stores it in the designated custom field on Jira. Congratulations! You have successfully mapped the area and iteration path to a Jira custom field. If you still have questions or want to see how Exalate is tailored to your specific use case, drop a comment below or reach out to our engineers.
