How to automatically update the Assigned To on a User Story when state changes in Azure DevOps Board - azure-devops

We have a typical board with the following columns.
New
Groomed
In Dev
Ready for QA
In QA
Ready for release
Released
When we click and drag a user story from one column to another, we'd like it to update the "assigned to" field automatically depending on which stage its in. We're not seeing any settings from which to accomplish this from the Azure DevOps UI. Any suggestions?

You could customize the Process to achieve what you want:
Customize States for each column in user story work item type (The process for your team project should be an inherited process). Go to the Organization Setting -- Process, choose the inherited Process your team project used, and then choose user story work item type. Click States tab and add appropriate states for each column. Check the following example:
Add rules for user story work item type. Click Rules tab, and add following rule for each State:

Related

Adding to State Picklist in Azure DevOps Service

I'm using Azure DevOps Service (the on-line version, not on-premise) with Agile methodology.
I'm trying to add a custom state of 'Testing'. I use the method described here, but this doesn't seem to work. I can add Testing as a column in the sprint board, but it doesn't appear in the State picklist values (I do understand that adding a column will not add a State).
How can I get this to appear in the State picklist?
How can I get this to appear in the State picklist?
1.You can quickly navigate to the process your current project belongs to via Project settings => Overview => Project Details.
Then you can modify the states there. If you want to add a Testing state to Bug WorkItem type, click the Bug and click the new state:
2.And we should know that only inherited process can be modified in this way. So we must make sure our project is created from inherited process. Otherwise the New State button is disabled.

Powerbi and Azure DevOps (online version) reporting when Backlog Level name changes

I'm attempting to utilize Power BI and the Analytics Views provided in Azure DevOps to create reports. I noticed an issue regarding the template(s) used that caused for no data to appear in the datasets in Power BI.
Scenario: If a user uses the Scrum template in Azure DevOps, it calls the Refinement Backlog level of work "Backlog items". If a user goes into change that to "Stories" it changes how the queries grab the group of work items in that level.enter image description here You can easily change the query to match the new name of the backlog level. You cannot add multiple "projects" to that query and see the data in the dataset if other projects are using the default name.
Issue: I attempted to change the name back to the original name of "Backlog items" instead of "Stories" and run the query in the Analytics Views to grab the data from multiple projects with the same "Backlog items" level but nothing appears in that project that was renamed back to the original name.
How to reproduce:
Open a project in Azure DevOps
Access Analytics Views
Under any Backlog query, edit and add additional projects to retrieve data in this view and save
Open Power BI and connect to the recently changed query
In Azure DevOps, access Organization Settings and go to Process
Access the project the above query is located and open the template
Modify the name of the backlog level to something other than "Backlog items"enter image description here
Save and go back to Power BI and refresh data
Actual result - you should not see the data from that project due to the name change
Go back and change the name back to the original name and refresh the dataset in Power BI
Result:
You still do not see the deta in the dataset even though you renamed it back to the original name. Besides 'resetting' the backlog level back to the original default state, is there a way to get it to recognize the original name if you renamed it back? Is there another step to making it recognize the name change? Since it's in the cloud, I waited 24 hours after the name change back to the original name but still didn't work. I noticed the same thing will happen on the Portfolio Backlog level (i.e. Epic).
Besides 'resetting' the backlog level back to the original default
state, is there a way to get it to recognize the original name if you
renamed it back?
I seem to reproduce similar issue like yours and then I use steps below to make it work:
1.Reset the Backlog and refresh the page.
2.Then navigate to the Analytics views, edit the View(the view in your step3) which can't be recognized now.
No matter it's Backlog items backlog or Stories backlog here, delete them all and Verify the view. Then click Save button.
3.Refresh current page and edit the View again, add the Backlog Items backlog back, Verify the view, Save the view. Now refresh the data in Power BI, the data should come back.
Above steps are what I use to work around the issue, hope it helps :)

Azure DevOps: Field with default value containing another fields value

I am trying to find a way in Azure DevOps of displaying a field on a User Story layout that is made up of a URL plus the value of another field on the same story.
We have an external support ticket system where all of our support calls are logged. When the story (or even Defect) is created, we have a field where a support reference is entered.
I want another field that combines a URL and the support reference so it creates a link to the support ticket.
Is this do-able?
Thanks,
Craig
This is achievable. You can Add a custom field to a work item type for an inherited process.
1,First you need to create a inherited process.
Go to Organization settings, From the Process page under Boards, open the … context menu of the process you'll use to create an inherited process, and then choose Create inherited process. Choose the same system process—Agile, Basic, Scrum, or CMMI—that was used to create the project that you want to customize.
2, Add a custom field to an existing work item type for the inherited process.
From the Process page of the selected inherited process, choose the work item type(User Story) you want to add the custom field to.
Select the work item type and click new field or ... to add a field under a group.
For example i add a new field Support Url under group Planning(click Options to define a default value for this field).
3, Apply the customized process to your project.
Click team projects of the process shown as below screenshot.
Open the … context menu for the process and choose the Change team projects… option.
Then you will have the custom field with default value for the work item type in your project.
For detailed steps please check Microsoft Document there.
Update:
Field value made up of a static part, plus another field
There is no direct way or any tool i can find to achieve this. However there is a complicate workaround to achieve this.
You can try creating a service server to to combine the field values and update the workitem field with workitem update rest api, and add a service hook to this service server.
You can refer to the service hook sever provided by Microsoft. Check reate a pull request status server with Node.js

How to default field based on project-level settings in Azure Devops?

I need to set a field on all User Stories, and that field will be the same for all stories within a project. Namely, I'm trying to assign projects to certain Project Leads and I want them to be defaulted as the Project Lead on all the user stories withing that project. How do I create a rule that will default a custom identity field to be the same for all user stories within that project? I'd rather not create a new Azure process for each new project. I want to be able to manually set some field on each project at the project level, and then have the default on my custom field in user stories within that project to be based on that project-level setting.
Currently this can't be done through process customization. Unless you create a custom process for each project.
The Aggregator-CLI can process a rule after a work-item is created/updated and you can use it to set these default values based on a lookup.
This one-click extension also makes it possible to run rules on the workitem form itself. It takes a different approach (runs in UI instead of from a servicehook).

Child work types inheriting field values from parent item

I am working through creating a custom process in Azure DevOps and was curious if field values from parent can be shared with child items.
Here is an example:
Create field 'Custom Field 9' on Epic work type
Create the same field 'Custom Field 9' on Product Backlog Item work type
Create an epic and fill in the value of 'Custom Field 9'
Create a child Product Backlog Item, 'Custom Field 9' is then inherited to the backlog items field.
What I've tried so far is to use a rule on either Epic or Product Backlog Item, however, I do not believe the rules can apply to creation of children processes.
One other option I'm going to try later today is a Flow that detects when a child work item is created and perform it automatically. I'd like to try to keep this contained to Azure DevOps if possible.
Edit: Thought it helpful to mention that we are using the hosted solution of DevOps and nothing on premise.
Sorry to say that as default, there does not such a work item features with "out of the box". But you can use another tool to achieve this.
Like you said, Microsoft Flow, there does not such feature supported while connect with Azure Devops.
But, in addiiton, I think you can do this with writing some custom scripts. And then configure Web hook to trigger this custom events.
Also, here has another tool named TFS Aggregator (Web Service) to achieve what you want. You can set and configure apply certain rules (such as copying fields from a parent item to a child item). And it will trigger after a work item is created or saved.
I know this is very inconvenient, here has an same feature suggest which raised by others. They has the same demand with you. You can vote and comment for this suggestion. When there are enough communities vote and add comments for this feedback, the product team member will take this feedback seriously.
I needed this feature as well, but in it's absence I have got it to work (relatively easily) with an Azure Logic App (for anyone also using Azure)
​Trigger
When a work item is created
Then
​Get work item details using "Parent" as the work item ID to search for
​Finally
​Update the new work item with any field from the parent you require
​
​