I have a User Story against which there is an impediment faced in current sprint. Due to this impediment, we are not able to complete the US in this sprint. However we cannot also close it or mark it resolved. Since its open without any action, its also interfering with the burndown charts.
Can I get an advice on how we can handle impediments in Azure DevOps and thereby set that work has been halted/suspended on a particular user story? I was reading the related article here: https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/manage-issues-impediments?view=azure-devops.
Thanks and Regards,
Satheesh Vijayan
As stated in the documentation:
You use issues or impediments to track items that may block work from
getting done. In general, you link these items to user stories or
other work items using a Related link type.
So as a workaround ,you can try customizing impediments tracking ,through this you can customize the item state,add a special state to impediment item . For details, see Customize an inheritance process.
Organization Settings -> Process -> Inheritance process -> Impediment ->State -> New state
Note: only inheritance process can be customized.
Related
How can I set that issue work-items should be required to have a parent item?
That would be very helpful in tracking work-items that are causing issues.
Thanks
So far, this action is not supported. We can make a requirement in “Organization Setting”→Process→Rule to restrict creating work item, but there’s no “Related work” and “Parent” option can be selected in “Make required”.
I found there’s already a similar feature request ticket submitted in Developer Community. If it meets your request, you can vote and add your comments in the ticket.
I want to pin a chart to the Azure DevOps Services dashboard that shows how many bugs in the current sprint have a linked test case or not.
I have been able to put up a query for the same but it appears that such queries can't be charted out. Is there an alternate way?
Here's the error that I get while creating a chart out of my query
Additionally, I would also like to know if there is a way to ensure that when I Resolve/Close a bug workitem in AzDo services, I can check if there is at least one associated test case work item with the bug. I have explored Bug rules but can't find out a clean way to get the link types associated with the work item. How can I achieve this?
Thanks
I have been able to put up a query for the same but it appears that
such queries can't be charted out. Is there an alternate way?
As for the error you got, it's one open issue here in our feedback forum, the product team is considering about it. But there might be some time before the feature comes true. You can track the issue to get notifications if there's any update. Sorry for the inconvenience.
Is there an alternate way?
If you just need a widget to display the results of the query, you can consider using Query Results widget, if supports tree or direct links. But if you do want the pie chart for WITs, I afraid it's not supported for now when using tree or direct links. You can check the related extensions here.
I have explored Bug rules but can't find out a clean way to get the
link types associated with the work item. How can I achieve this?
As I know we don't have such option in Azure Devops Boards.
If we close/delete one workItem, it won't display a prompt or what that tells us the related workItems are still active.
But I think that would be a great idea, so I suggest you can post one feature request here to share your idea to product team. Then we can share the feature request link here and people who interested in that would vote for you! Hope all above make some help :)
In Azure DevOps Boards, if you open a work item and reference another in the discussion field by using #ID for the work item you want to discuss, ADB automatically relates those two items.
More recently, the dev team has determined that the code review tool they are using is tying reviews to multiple work items because of this related field.
Other than telling the team to avoid using the #ID feature or manually removing related work items from each story and task, is there a way to prevent #ID from relating work items, but still allowing the live link in the discussion thread?
The #ID control quickly links objects to work items. With this control, you can specify or select a work item ID and it's automatically linked to the object.
Use the #ID control within the following areas:
A work item discussion or any rich-text field
A pull request discussion
Commit comments
Changeset or shelveset comments
Wiki page
Is there a way to prevent #ID from relating work items, but still
allowing the live link in the discussion thread?
Sorry it's not able to do this. This is by designed, it will automatically link to the object in Azure DevOps.
If you really do not want this, you may have to avoid to use #ID or manually remove the link relationship.
More details about link work item you could also kindly refer this official tutorial.
for Azure DevOps 2019/2020
You could enable or disable commit mention work item resolution , for details you could visit : https://learn.microsoft.com/en-us/azure/devops/repos/git/resolution-mentions?view=azure-devops
I've test 2019 and 2020 version , it works fine for me.
When we are doing the customization of a work item type in VSTS. Do we also have the ability to track the history of the customization itself?
For example, we are trying to find out when the start date field was added to our customized Bug work item type.
A field was not there in a previous Increment but we noticed it recently. Just want to find out if there is a date captured somewhere that tells us when it was added or who may have added it?
Unfortunately we cannot get the information from VSTS for now. No date or history included from the retrieved process information via REST API.
However there's already a user voice submitted here to suggest the feature to add Activity Log to VSTS to track user accesses, you can go and vote it up or submit a new one to suggest the feature again to achieve that is future release.
For now as a workaround we suggest that you can ask the team members to add corresponding comments in description area after completing the customization for the process... Thus you can track the history of the customization...
I have a workflow that runs upon the change of status of an entity (Opportunity "Won"), in which I am creating another entity.
I want to copy all the notes from the Opportunity to the new entity, but I cannot see how to do it.
Is this possible without coding (or in fact, with coding!)
Chris
Its not possible without coding. With coding (custom workflow activity and the ICrmService) you can read and creates notes (Entity: annotation).
I agree with benjynito answer. You need to hook a custom workflow activity in order to get the notes object.
Here is the link to setup a basic custom workflow activity : http://www.stunnware.com/crm2/topic.aspx?id=CustomWorkflowActivity
An example of some custom activities on CodePlex: http://crm4activities.codeplex.com/
Custom workflow activity documentation on MSDN: http://msdn.microsoft.com/en-us/library/cc151142.aspx
It is possible to do this using the clone children action in "Dynamics 365 Workflow Tools". I used this library to copy the notes from a lead to an account when the lead is qualified. For exact steps see the documentation of clone children or my blog post Copying Notes from a Lead to an Account that shows you how I did it for notes.