Azure DevOps
1381 TopicsCan we integrate azure board in java application for retrieving projects, work items operations
I want to integrate the azure board in my spring boot java application to fetch the projects, iterations,work items. does azure provide the sdk for it so i can use that jar and integrate this kind of operation in my application. does azure sdk has dedicated methods for azure board data like project,iterations , work items27Views0likes4Commentsazure board what is the max page size limit for get project level iteration api
i am using classificationnodes iteration api what if the number of project level iterations exceeds this limit how can we retrieve the next set of iterations using pagination? can we use filter as search iterations by name ? can we user top and skip for this api? please explain the use of parameter and any example if possible.26Views0likes2CommentsHow to sync Text, Date, and Dropdown Custom fields between Jira and Azure DevOps
Jira Azure DevOps integration is the need of the day. Both platforms offer robust features but when it comes to integrating data like custom fields, things can get tricky. This is where tools like third-party integration tools can help, ensuring your custom data flows effortlessly between Jira and Azure DevOps. In this blog, we'll dive into a common use case: syncing custom fields between Jira and Azure DevOps. We'll explore the key custom fields—Text, Dropdown, and Date—and provide code snippets to illustrate how third-party apps can make this process straightforward. Why sync custom fields? Custom fields allow teams to capture unique data that goes beyond standard fields like summary or status. By syncing custom fields, you ensure that all teams, regardless of the platform they use, have access to the same critical information. This leads to better collaboration, reduced errors, and a unified workflow. Setting up the environment for syncing custom fields between Jira and Azure DevOps We will use a tool called Exalate for this article. Start by installing Exalate on Jira and Azure DevOps from their respective marketplaces and connect them using the Script mode. The Script mode has incoming and outgoing sync rules written using low-code Groovy scripts. You can edit them at both integrating ends to meet your sync requirements. To send custom field data from a Jira issue field to its corresponding Azure DevOps work item field you’d need to modify the outgoing sync rules of your Jira instance. You would also need to receive the data coming from Jira in some work item field. For this, you’d need to modify the incoming sync rules of your Azure DevOps instance. To do this the other way around, simply reverse the codes in the incoming and outgoing sync scripts. That's all! Set an automatic trigger as the next step and see your data synced smoothly between the systems. Custom fields sync: a deeper look 1. Jira to Azure DevOps text field sync Text fields are commonly used to capture detailed information. Whether it's a technical description or customer feedback, syncing text fields ensures that all teams have a consistent narrative. //Jira outgoing sync replica.customFields."CF Name" = issue.customFields."CF Name" //Azure DevOps incoming sync workItem.customFields."CF Name".value = replica.customFields."CF Name".value Here, we simply map the text field from Jira to Azure DevOps and vice versa. Exalate takes care of the data transformation and transmission. 2. Jira to Azure DevOps Dropdown (select List) field sync Dropdown or select list fields are perfect for categorizing information, like selecting a priority level or feature type. Syncing these ensures that the categorizations are consistent across platforms. //Jira outgoing sync replica.customFields."CF Name" = issue.customFields."CF Name" //Azure DevOps incoming sync workItem.customFields."CF Name".value = replica.customFields."CF Name".value.value The code snippet captures the dropdown object with its values in one platform and assigns it to the corresponding field in the other. 3. Jira to Azure DevOps Date field sync Date fields are essential for tracking deadlines, milestones, and other time-sensitive data. Keeping dates in sync prevents miscommunications and scheduling conflicts. //Jira outgoing sync replica.customFields."CF Name" = issue.customFields."CF Name" //Azure DevOps incoming sync import java.text.SimpleDateFormat .... def sdf = new SimpleDateFormat("yyyy-MM-dd hh:mm:ss") def targetDate = sdf.format(new Date()) //throw new Exception("Target date = ${targetDate}") workItem."Microsoft.VSTS.Scheduling.StartDate" = targetDate This snippet ensures that the date values are synchronized, keeping project timelines aligned. Best practices for syncing custom fields between Jira and Azure DevOps Consistent field types: Ensure that the custom fields in Jira and Azure DevOps have compatible types. Field mapping: Carefully map the fields to avoid data loss or misinterpretation. Testing: Always test the sync setup in a sandbox environment before deploying it in production. Conclusion Synchronizing custom fields between Jira and Azure DevOps can enhance your project's efficiency and transparency. It ensures all teams have access to the same data, regardless of the platforms they use. Ready to sync more data between Jira and Azure DevOps? Drop a comment and we can discuss.29Views0likes0CommentsCompletely migrate DevOps Organisation to new Tenant and Subscription
Hi, hope this question besides here. Can anyone confirm the steps needed to completely migrate a DevOps Organisation to a new Tenant and Subscription. The first steps are obvious: Prepare new AD Tenant Switch AD Connection (Switch to another Azure Active Directory - Azure DevOps Services | Microsoft Learn) Currently there is a MPN Subscription in use (also for DevOps billing) even with that i don't see problems, as we could change the billing Sub to f.e. a PAYG Sub during Migration. The main concern is about whats "inside" our projects: We use ServicePrincipals for deploying into AppServives and others We have some service connections to GitBucket and other Even if the change to the new AD Tenant and billing Subscription goes smooth We would need to recreate all ServicePrincipels at the point we would migrate our AppServices and other services in to a subscription within the new tenant? Even if we migrate out MPN Subscription (via support case) we would need to create all needed SP in the new tenant and modify the pipelines which use them. Are we correct? Did anyone else a migration like this on? Appreciate all your feedbacks Regards, BenSolved39KViews0likes8CommentsSign in to Azure DevOps
The https://dev.azure.comURL redirects to the landing page for the Azure DevOps product. I used to promote this as an URL to use to login to the product. Since this year the page is missing the "Already have an account? Sing in to Azure DevOps" link. As far as I can see there is no way to login to Azure DevOps trough this interface now. There is the usual "sing in" in the top right, which will redirect you to the azure portal (or at least for me it does). How are we supposed to login to Azure DevOps? Old login:Solved349KViews4likes9CommentsIs there a way to subscribe to release notes by Azure Devops?
Hello, I'm trying to find a way to subscribe Azure Devops release notes that are provided in the link below in a way that can automatically update myself and/or our scrum teams when new features are deployed to Azure Devops. I tried the "subscribe to updates" link in the navigation pane but it doesn't seem to do what I'm looking for...is this possible? I just want our teams to be notified when Azure Devops publishes new release notes. https://learn.microsoft.com/en-us/azure/devops/release-notes/2021/pipelines/sprint-184-update1.7KViews0likes3CommentsDatabricks Job owed by service principal, failed to checkout from Git repository : PERMISSION_DENIED
Hello, I'm working as Data Scientist and I have some jobs to run on a Databricks. I've created the jobs, which run the code store in an Azure DevOps repo. Everything went well, when I tested the jobs, all worked well. I transfered the ownership of the jobs to a service principal (this way : https://learn.microsoft.com/en-us/azure/databricks/workflows/jobs/how-to/run-jobs-with-service-principals), and since, I get this error message : First I though it was because the service principal wasn't in the list of authorized users with "Read" permission over the repo that contains the code, I added the service principal as a user in my Team's Group, and now it has the following permissions over the repo (I followed this tuto :https://techcommunity.microsoft.com/t5/azure-devops/how-to-grant-service-principle-access-right-to-azure-repos/m-p/3744052) : But I still get the same error. So what's happening ? How can I fix it ? Thank you Charlotte1.7KViews0likes2CommentsHow to export process template and import into another organization using azure devops api?
I want to export process template from one organization and import into another organization. I am referring the documentationexport/import process template I want to achieve few things like If template not exist then it should create into another organaization If template exist then it should add all new workitemtype and its setting if workitem type exist then it should override the existing setting and new setting should be added for existing workitem type How can I achieve mention points?2.4KViews0likes2CommentsCompile From Azure Pipeline ignores certain files related to CefSharp nuget package
Good day to all, We are developing a WPF Desktop project that uses the nuget package "CefSharp.Wpf.NETCore". When we build this project from Visual studio manually (in both debug and release mode), some files are generated in a folder that is a subfolder of the bin folder. Attached is the screenshot below: So far so good. But we have automated the build and release of our WPF software using Azure pipelines. When we run the build pipeline, it runs without any error. But certain files are missing in the folder shown above in the screenshot. Since certain files are missing, when we run the WPF.exe, it gives us exceptions when we run the program. Attached below is a screnshot that shows the files generated from build pipeline. Comparing both the screenshots reveals that when the WPF project is built in azure pipeline, certain files are ignored. These files are related to the nuget package"CefSharp.Wpf.NETCore". Any idea as to how to solve this would be appreciated. Attached is the screenshot below that shows the azure build pipeline.565Views0likes2Comments