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

Post a Comment

Popular posts from this blog

Azure Devops Bypass policy when code push - Glimpse Devops is a culture most of the organizations embrace it. In this article let's see what is branch policy in Azure Devops (ADO). Before that, we need to know what is policy (aka) Branch policy in ADO Branch policy has set of policies to be applied on the branch typically main. By that we avoid accidental activity. Few are as Reviewers required to view the code change before move to main/master branch work item - ADO's user story / task / bug etc., any of the item number should be linked Consider a scenario that your organization's existing project has some policies like most recent code pusher can not push code again. Very rare case may happen or not, a senior developer needs a exclusion to fix an urgent pre-prod/production incident. So He/She does not want to be in that case. They want to push their code often when discussing with client manager or customer So, how can we override the bran
Post a Comment
Read more
Find your azure service/resource tab easily in chrome using an extension Irrespective of role like Azure devops, developer, network engineer, architect etc., we typically use azure portal primarily While working on issues and/or in presentation, we may require to have multiple azure tabs with different services Here consider a scenario that I am analysing an issue from logic app which uses azure function. So I need to visit logic app, function app and application insights if enabled. If we use single tab, it will take more time. So, we can have multiple tabs. Here logic app, azure function and application insights in each tab I would have. yes. It will save our time but consider that sometimes we would have more than 10 tabs at that time we may not know which tab has which resource because all browsers have A icon. So, while navigating, we may get annoyed. So, What's the solution when we use more tabs? Here we've a nice feature in chrome browser which provid
Post a Comment
Read more
Azure storage account new access tier - Glimpse Azure has introduced a new access tier for storage account called 𝐂𝐨𝐥𝐝. What is the use of it where we already have 3 access tiers as 𝐇𝐨𝐭, 𝐂𝐨𝐨𝐥 𝐚𝐧𝐝 𝐀𝐫𝐜𝐡𝐢𝐯𝐞? Let us take scenarios as below. When our document will get frequently accessed - 𝐇𝐨𝐭 When my document will be infrequently accessed (i.e Within 30 days, it can be accessed. - 𝐂𝐨𝐨𝐥 If my document will be accessed after 30 days, 𝐞𝐚𝐫𝐥𝐢𝐞𝐫 𝐰𝐞 𝐠𝐨 𝐟𝐨𝐫 𝐀𝐫𝐜𝐡𝐢𝐯𝐞 access tier but now When my document needs to be accessed within 90 days at any time - 𝐂𝐨𝐥𝐝 Data retrieval from Archive needs some process like rehydrating (i.e converting from Archive tier to (Hot or Cool) aka offline tier to online tier). To save some cost, we can go for cold tier which allows us to keep our data for 90 days instead of archive tier. Limitations and known issues. The change feed is not yet compatible with the cold tier. Object rep
Post a Comment
Read more