I've done some searching but can't find an answer to this. In our current Test Case Management System, we have an option to archive Test Cases which are no longer relevant (eg because an API or UI option was removed). The TC still exists, but just cannot be executed in any Test Suites any longer.
However, I cannot find any such option in Azure DevOps ... is there ? The closest I can find is deleting a work item, but that's obviously not what I'm after. I know that other work items (stories, epics, bugs etc) have a defined beginning and end, but TCs tend to stay around as long as they are relevant (for automation/regression testing etc), so I feel they should have a slightly different lifecycle than other work items.
Anybody found a way of doing this in Azure DevOps or found an alternate solution ?
There is no out-of-box features for that. You may try on of these suggestions:
Just add new tag "Deprecated" or "Archive". Add work item tags
Add area path "Archive" and move work items to it. Define area paths
Edit your process template and add new state "Archive" to "Remove" category in the test case work item type. Add a workflow state
Related
We've been using environments for a while now for our dev and test instances. I like being able to go to the environment and seeing the commits and work items associated with the particular build/release but can't find a way to export them. Does anyone know of a way to export the workitems?
Using environments you also loose the ability to see which build/release a ticket went out in or have I missed something?
Your first and second question, kind of, have the same answer.
In short, you don't want to be using Environments to view which work items are associated with a release.
Azure DevOps has a built-in mechanism to view work items directly within the Release or Pipelines page (Depending on whether you're using classic or YAML).
Here is a great guide published by Microsoft regarding how work pipeline-based work item linking works, as well as how to retrieve work items associated with a release:
https://devblogs.microsoft.com/premier-developer/how-to-retrieve-all-work-items-associated-with-a-release-pipeline-using-azure-devops-api/
Update:
Specifically regarding how to view linked work items in Pipelines. You'll want to look under "Related":
Clicking on "x work items" will show you the full list of work items:
I want to restore the state my project was in 11/10/2021 into another temporary project (not the one I am currently using), so I can only grasp the order of work items from Backlogs from Boards for that day. I did not delete the project. I just changed the Area Paths for Teams and the order of work items changed. I just want to have a reference in a separate temporary project, so I can compare work items order between them and restore correct one to the actual backlog.
Doing something like this is going to be quite tricky, I think that the closest you will come to doing this will be to create a new project and then try to use the open-source migration tools at https://marketplace.visualstudio.com/items?itemName=nkdagility.vsts-sync-migration. We used an earlier version of this for an Azure DevOps carveout from another tenant, and it worked well, but we didn't have your "restore-to-point-in-time" use case.
I think that what you're going to need to do is use the ReplayRevisions on the WorkItemMigration class, and then you're probably going to need to write some custom WIQL to get only what you're looking for. It's even conceivable you might need to extend this to get the functionality you want.
I have problem with configuration of AzureDevOps process.
My goal is simply automate work items - when work item changes state to done or is in state done on certain board I want to transfer it on other board.
I tried to achieve this by applying custom rules in my organization. Example:
I navigate to Organization Settings, select Process then I select process from list (is inherited from Scrum parent). Then I select bug (for example) and go to rules tab.
Here is screen of my configuration
Both Board no.1 and Board no.2 exist as Team Projects. I've added clearing assign to field and this one works properly.
I wondering if there is much easier way to automate moving work items through boards or team projects on status change.
I wondering if there is much easier way to automate moving work items
through boards or team projects on status change.
For this issue, I am afraid there is no easier way to achieve this requirement. Azure Devops has provided a built-in custom rule function to achieve this. This is already a very easy way.
In addition, we can also achieve this through the azure logic app, but this needs to be set in the azure portal. I don’t think it will be more convenient than custom rules.
To move work items to another project, you must be a member of the Project Administrators group or be granted explicit permissions to move work items.
On the Azure DevOps TaskBoard for a sprint, it would appear that the only thing I can drag across the board is Tasks. Not bugs. Not Backlog items. Which means if I want to see where a bug is on the board, I have to create a task for it. (Note: My project uses Scrum. Bugs are managed with requirements)
I guess this makes sense. It is a "Task board" after all. But this seems tedious. Most of the time, the bug is the task. I make a bug, make a check in, and mark it done. I would expect to be able to drag the bug itself across the board to mark it done.
And even if I go to the trouble for creating a task for a bug (or a Backlog Item) and then I drag the task across the task board to "Done", the bug's status still stays where it was. It doesn't change to not done. I then have to go to the bug and manually mark it as "Done"
This really limits the usefulness of the Taskboard for our planning.
Am I missing something? Is there way to change this?
You can choose to manage the Bugs with tasks as Daniel commented. And You can use extension Work item form one click actions to assign the Bug to some parent PBI automatically. See below example:
First you need to install Work item form one click actions extension to your Organization.
Then Go to project setting page-->WIT One Click Actions under Extensions-->Bugs-->Create rule group-->New Rule
Triggers: New work item load
Actions: Link to an existing work item(relation type: Parent; Work Item id: Id of PBI)
After above rule is created. The newly created bugs will be automatically added to the parent PBI you specified in above rule.
However, The PBI and Bugs(managed with requirements) can be moved around in Boards. So you can use the filter to view your work items in a specific sprint.
We have a project that often has the exact same work flow needed.
We have a feature that includes detailed work items, along with very helpful descriptions.
Is there not a way to take a current Feature and duplicate it along with all of the work items?
I have tried using templates but that has not worked out.
I tried Copy Work Item and checked 'Include existing links' but it does not copy the Related Work, which is what I need.
To further clarify I would like to duplicate a Feature, along with its Product Backlog Items and their Tasks.
You would be able to use powershell and VSTS REST API to achieve this copying. A sample powershell is available in the thread here
You can modify that and create a script to support your needs.