Skip to main content

Azure Devops - work items bulk import-update-publish to Devops using Excel

#cloud #azure #devops

Hi All!

As a azure devops guys and work on scrum or any other methodologies, we have many chances to update our tasks in devops.

There are chances that project manager and/or project lead need to work on consolidated work items for presentation.

We can update our task one by one individually which takes more time and Consider the below scenaio.

  1. Project lead or we need to modify the state of 100 work items.
  2. More than 15 work items title need to be modified.

To achieve the above with minimal effort and time, we have Azure Devops Office Integration feature which will help us to work on excel and update the work items altogether from excel to Devops all at once.

Here before, we used query in Devops and then we would export into CSV. Now with the help of above software, we can work in an excel for updation very easily.

Please look into the below images.

In the first image before installed the software, we have no Team option. After installation we could see it at the end of menu section.

In the second image, after clicked the New List

  1. we need to connect to our devops organization/account
  2. Select the project from where you need the task(s)

In the third image, I modified the titles of 2 work items and then publish them. After publish and refresh the devops page, published changes affected in Devops

We can change the state of multiple tasks all at a time and publish.

In this post, I used only 2 work items for an illustration but it helps us for lot of work items altogether all at once.

To Download the software, Click the below link
Azure DevOps Office® Integration 2019

Hope this post will be helpful. Play around it. Cheers!

Comments

Popular posts from this blog

Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
Azure Public IP(s) are zone redundant free of cost natively - Generally Available Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter. Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase. Public IP helps to access a resource or an application publicly. Azure offers 2 types of SKU for public IP as below Basic Standard Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025. Standard public IP can be fell into any of the below category No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...