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.
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'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
I want to reorganize my variable groups in Azure DevOps, but before I delete any variable groups I want to make sure they are not used anymore. Also I need to link the newly created groups to old releases.
I could go over all release definitions and check which definition is linked to which variable groups, but there should be a more easy way for me show if a variable group still has linked releases. But I cannot seem to find that overview.
Is there an overview like above of will this be a pain in the ... to reorganize?
I don't see it available either, from the front-end or documented as available from the API. I think your only option is the one you mentioned to loop over the definitions to validate.
Looking at Task groups, they included a References tab which is probably what you want just on the Variable group. I'd recommend creating a feature request for this on the developer community.
Our company currently has about 10 active projects and 5 programmers.
My manager wants a weekly update on all open items, just a list of them.
I only need the list for our organization, not across multiple organizations.
I can see all open items assigned to me, but I cannot seem to figure out a way to see all open items across all projects.
Is there a way to do this without having to go to all 10 projects then manually compile this list?
It is looking like we have perhaps set stuff up less than optimally.
Is is perhaps better to use less projects and group work differently?
Joe
Hmmm...reading this:
When to add another project In general, we recommend that you use a single project to support your organization or enterprise. A single
project minimizes the maintenance of administrative tasks and allows
full flexibility to cross-link objects.
from: https://learn.microsoft.com/en-us/vsts/organizations/projects/about-projects?view=vsts&tabs=new-nav
makes me think we may have setup or organization wrong. It would have been great if this was made a bit clearer in the documentation. This is the first I have seen this.
You can use a query and check the "Query across projects" checkbox:
For example, this query give you all the bugs in all projects with state "In Progress":
You can save the query and display the results on the dashboard or export to Excel with this extension.