We're currently using Azure DevOps to manage work items (user stories, task , etc.). I'd like enable an event/trigger when I close the user story, the child task-status are also closed. Is this possible?
I saw within
User Story State Change to Update Work Items
Generally, we would like convert the parent work item state based on the linked child work item state, not the other way around.
Converting the child work item state based on the linked parent work item state may cause some unsafe issue. For example, if we have one child work item that is not completed, then we accidentally closed the parent work item. In this case, the incomplete child work item will also be closed incorrectly.
To resolve auto change parent states, there is a free solution on the marketplace available: TFS Aggregator, For VSTS, you need to use Web Hook to complete it. Please refer to this : https://github.com/tfsaggregator/tfsaggregator-webhooks.
Besides, if auto change the linked child work item states is your final requirement, You can use the Rest API to invoke state changes. You could check the post and the post for some more details.
Hope this helps.
Related
Is there a way to query product backlog items (and their histories) to find what the parent of an unparented task was before the link was deleted?
For instance here I have two tasks that are showing up as unparented.
They used to be parented to a user story but the link has been broken. Rather than having to trawl all my user stories and look through the history, I would like to be able to run a query (for instance on item 253152) and it to tell me what the parent used to be.
Update 07 Apr 2022:
Miao Tian's answer is of course absolutely correct.
In our case the tasks appear to have never been parented. They where created by a third party tool which appears to have failed to link them correctly. I'll post more information if it is helpful when we get to the cause.
If you just need to find the parent of this work item in the past, you don't need to use query. You can directly open item 253152 to view its history.
example:
start
delete the link
check the history of the task and find the parent
In my organization we need to configure work items to require the field callled parent, also I want to know if it´s possible send a warning for all the work items previously created to be fixed by the assigned people.
I expect when someone will try to create a work item would be necessary add a parent item to complete the creation and I hope update the previously work items quickly or in an automation way.
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.
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
I'm trying to add a new state to the user story Work Item type in VSTS. To do this I follow the instructions outlined here:
https://www.visualstudio.com/en-gb/docs/work/process/customize-process-workflow
However, when I get the states page the "+ New state" option is greyed out and I cannot click on it. I am a member of the "Project Collection Administrators".
Can anyone tell me how to enable the "+ New state" button?
So VSO has this Hierarchy like there are Processes which can be considered as your SDLC ( Agile, CMMI and Scrum). These are System defined processes and we cannot edit them. And Each Process can have many number of Work Items associated with it. System level process cannot be edited meaning you cannot create, edit, create state for a system process. The work around is to create a Inherited Process with the Available System Processes, which will also inherit the Work Items. This inherited process can be edited (you can create, edit, create state for the work items available in this inherited process). So keep in mind while inheriting from any process, for which work work item you want to add state and create a inherited process from that parent process.
Please follow this link to create a inherited process : https://www.visualstudio.com/en-us/docs/work/process/manage-process
Also keep in mind that whatever project you create has to be based on the inherited process so that the changes that you make in the customization is available at the Work Item form level.
Hope this helps.
Thanks,
Bhadhri