I was inspired by the One-Page PRD mentioned on the Atlassian website.
How might I go about doing the same if I am using Team Services? For example, lets say I have an Epic and linked underneath that several features, user stories and acceptance criteria. Is it possible to create a "one pager" based on just this epic that summarizes all the items underneath it at a glance? (for example: lists the epic's description at the top, followed by all the user stories with description and current status, and acceptance criteria met or not met underneath?) It would be useful for distributing to non-technical product owners instead of having them wander through work item queries to get an overall picture of the project with some requirement detail, or to present to stakeholders during a meeting.
Most of the reporting options I am finding, such as the built in dashboards (and Power BI?) are mostly aggregate charting. It would be simpler to create what I need in SSRS, but my understanding is that is not available with Team Services.
As you said that the Team Services has built in dashboards and integrate with Power BI, but aren’t meet your requirement.
For your requirement, you can build a custom extension (e.g. Dashboard widget) with REST API (can call rest api with VSS sdk, check dashboard widget sample for detail) to do the report.
Related
We are using Azure Devops for requirements and manual testing. Looking for a way to use the oData connections to Power BI to create a traceability report that will link Features all the way to latest result of a test that should verify that Feature.
Data is organized such that:
Features = Business Requirements
Stories are linked back to Features as the instructions to the developers on what to build.
Stories are also linked to Test Cases that should verify the story
Test Cases are assigned to Plans and Suites for organization.
In DevOps natively we can pull reports for the results within the Test Plan, but we really want a full traceability report that link the chain together: Features > Stories > Test Cases > Latest result.
Ultimately we want both a tabular traceability matrix report as well as the ability to generate chart off that data.
Getting the lastest results off the Test Points linked back to the Cases is no problem, but we're sort of stuck trying to link back further to the Stories and then the Features.
Thanks in advance.
We are working on implementing an architecture review which affects a specific subset of work items. I created the following query:
The result includes the downstream work items, which is what I want. However, it also includes the work items marked as with the Architect Decision, which I don't want. My ultimate goal is to see on a dashboard how many work items are blocked by architect decisions which are pending.
AzDO does not support that. If you want to see a plain list, you should use a flat query. As workaround, you may write your own job through REST API (as example):
Find epics, features, stories, and bugs without the Blocked by Architect Decision tag and with open work items contain the Architect Decision. Add to these work items the Blocked by Architect Decision tag.
Find epics, features, stories, and bugs with the Blocked by Architect Decision tag and without open work items contain the Architect Decision. Remove from these work items the Blocked by Architect Decision tag.
Then you can search your blocked work items with a flat query and the Blocked by Architect Decision tag.
The Rest Api methods:
Query By Wiql.
Update a work item tag.
Additionally, you`ll receive a notification when your work items are unblocked.
Our team is currently using DevOps and are very pleased with how everything is working. We've setup Dashboards in each project that tracks work items and sprints and would like to do the same at the Organization Level. Is there a way to create a master overview of multiple projects in an organization?
Unfortunately we cannot create an organization level dashboard, it's not supported.
We can only create the Team Project level dashboards for teams, please see Add and manage dashboards for details.
However there's already a user voice submitted here to suggest the feature and it's in planned, but based on the response seems no plans to store a dashboard on organization overview. So you can vote it up and add your comments on the existing user voice or submit a new one to suggest the feature...
In our VSTS Feature
Timeline(https://learn.microsoft.com/en-us/vsts/release-notes/), you
see a feature called “Dashboards – Create dashboard separate from a
team” under “Reporting”
This feature will allow you to create a Dashboard that has no
association with the team. This means you don’t need to create a team,
to make a Dashboard. You can create any number of these Dashboards and
share them with who you want.
However, Dashboards will still be stored with a Team Project. So to
address your scenario (cross-team-project Dashboard), you’ll just have
to pick a team project to store the dashboard.
We don’t have immediate plans to store a dashboard outside a team
project.
Our team was dealing with the same problem as yours, and we decided to develop our own dashboard solution at the end.
After using it as an internal tool for several months, we recently made it available as a SaaS.
You may check it out on meercode.io for more information.
Your feedback will be greatly appreciated.
Behind the dashboard widgets are queries, and it is possible to execute those queries across multiple projects.
When you open the query editor, there is a checkbox:
"Query across projects" checkbox (imgur)
This way we created a project in Devops that only contains a dashboard that shows all work items in any project, assigned to or followed by the current user.
That and some nifty colored tiles =)
I am building a VSTS dashboard widget where I would like to iterate over all Features in a particular Epic, and then for each Feature gather data about all the WorkItems to create a status report.
I know I can use getWorkItem() and getWorkItems(), but that is if I already know the WorkItem IDs. I want to loop through all the features and then all the WorkItems and see if they are completed, without knowing their particular ids.
The VSTS work item tracking system is very extensible, therefore there aren't any "fixed" methods that will return you specific work item types. Even though features in VSTS rely on one or more levels of work items being present, their name, the fields and other aspects of these work items are highly configurable.
To query the available work item levels (called Categories in VSTS), you can use the Categories/List API. This will allow you to find hierarchy as it's configured in VSTS and which work item types are available at each level.
You can use the ProcessConfiguration/Get API to list the relationship between the different backlog levels. Which is a parent of which and what type of backlog it represents. Is it a Task (lowest level), Requirement (Story, PBI level, planning level), or a Portfolio (Epic, Feature etc) level backlog.
With this information, you can either use the Backlig/GetBacklogWorkItems API to fetch all the work items on a specific backlog or you can construct a WIQL (Work Item Query Language) query to retrieve all work items that match that specific query. You can either export the WIQL from Visual Studio or use an extension.
Depending on what you need with each work item you can either query directly for the required fields, or just query the work item ID's and fetch the work item details individually using the workitem/getWorkItems(id) API.
There is pretty extensive documentation available on each of these API's and on the required VSTS services you can use from your extension. going deep to explain each of the services goes too far for this answer. I suggest you start experimenting from here and ask new questions as they arise. You now have far more information to work with and it will be easier to ask targetted questions from there.
I would like to move the backlog items and any related linked items to another tenant, any ideas?
There's nothing built in that does this.
You'll either have to write your own solution or look into one of the various migration or integration tools that are available on the market. None of them provide full fidelity migration, however.
As Daniel said that there isn’t built-in tool.
You can build an application with REST API to create the new workitems per to the workitems in another VSTS. Regarding Work Item creating REST API, there is bypass rules that can remain System.CreatedDate and System.CreatedBy value: Make an update bypassing rules.
On the other hand, there is 3rd tool: OpsHub Visual Studio Online Migration Utility