I need to display a table that has the following. Please help
enter image description here
for each team member total number of hours worked on a bug or task group by user story
I am not sure where do you want to display this info, but DevOps offers you have some posibilities. First of all you can make a Query. There are inside Boards -> Queries. There you can build a query of whatever you need, PBI, Tasks, bugs, hours... The first time migth be a bit trickie, but you have several posibilities.
In adition if you want to have a pretier visualization, you can show this info in the dashbord, located in Overview -> Dashboards. There you add a new dashboard or edit an existing one, and add a new widget as the next picture:
Then you can configure the widget with the query you did. You must set the query as shared fore this.
Is there a way to make a query criteria as customizable from the dashboard widget? Say for example, if iteration path is one of my query clause, I want to change the value in run time from the widget to generate the results. Right now am using the query results widget.
Is there any widget in marketplace which provides this feature?
Thanks.
Is there any widget in marketplace which provides this feature?
I fully understand your needs, but I am afraid there is no such widget in marketplace which provides this feature at this time. Currently, the query results widget is the closest extension to the demand.
If we want to add a custom query criteria on the dashboard widget, we have two directions to achieve it. One is adding query criteria to perform a second query on the results of Shared Queries, another is reflecting the query criteria set on the widget to the Shared Queries criteria and modify the original criteria. Obviously neither of these two methods are easy to implement, and there is still a long way to go.
In my opinion your request is reasonable, you could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
I have connected excel with AzureDevOps, as explained by microsoft
https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/office/bulk-add-modify-work-items-excel?view=azure-devops
Is it any way possible to export the Parent Work ID in the same row in excel as the actual work item that I am exporting?
What I want to achieve is to sum all remaining work that is left on feature level. This means I need to summarize the remaining work for all tasks under all users stories that belong to this feature.
I could fix this by adding tag of the parent feature in all tasks, but I want a better way.
There can be only one parent. Is there any way to export the parent ID?
Thank you.
Excel can`t import an id of linked work item in the same row. In your case, work items have to contain a parent ID in separate field. I see two ways to resolve your issue:
Create a new field for parent work item types (e.g. summary work). Then with custom solution fill that field with sum of child work.
Create a new field for the child work item types (e.g. parent id). Then with custom solution copy into that field a parent work item id.
Additionally, to avoid customization of your process template you can use Power BI custom reports (Analyze and report on your work using the new VSTS analytics service : Build 2018).
Using excel for analyzing the AzureDevOps work did not really work for all use cases.
The main reason was the ParentId. But basic graphs its easy to do.
Since then I have started using PowerBI instead. And I have managed to achieve all my requirements. After the initial setup its very straightforward to build custom reports in PowerBI.
Azure DevOps has introduced a new feature to make the Parent column available in queries.
Add parent field to backlog and queries
"The parent field is now available when viewing backlogs and query results. To add the parent field, use the Column options view."
I need to filter a a table with parameters that are calculated on a non related table, but to do this in Access web I need to add the [Project_Id] to the task list.
To clarify further, the user answers some questions regarding the details of a project, which in turn will calculate in the background a group of parameters that are needed to sort a task list.
The problem is the task list is generic and not related to a project so before I can use the project related filter parameters I need to assign a project id to the task list or there is no relationship and no way of knowing what project parameters to use.
I tried to do this with a query but being a Web database I am unable to select the data from the form control.
Hopefully someone can help me find a solution, because I have exhausted Google and my own knowledge on the subject. One last thing I am unable to use code thanks to security issues.
In case anyone is interested I found away to assign the project id to the task list using data macros.
The data macro is assigned to a table that is related to the project and when updated edits the tasks list to add the current project id for each record in the table.
I still have some issues to work around, but in general it does what I need.
I need to create some functionality in our SharePoint app that populates a list or lists with some simple hierarchical data. Each parent record will represent a "submission" and each child record will be a "submission item." There's a 1-to-n relationship between submissions and submission items. Is this practical to do in SharePoint? The only types of list relationships I've done so far are lookup columns, but this seems a bit different. Also, once such a list relationship is established, then what's the best way to create views on this kind of data. I'm almost convinced that it'd be easier just to write this stuff to an external database, but I'd like to give SharePoint a shot in order to take advantage of the automated search capabilities.
Proper Parent/Child in Sharepoint is near impossible without developing it yourself. There is one approach to that here: Simulate Parent / Child relationship in SharePoint 2007 with Folders & Content Types
(Note: This concerns SharePoint 2007. In 2010, Joins make this much easier)
Do it in a separate database, create a page(s) with controls that surfaces the data and run search over that. Loses quite a bit of the SharePoint features though.
Otherwise it may be okay to create a custom field control that will allow you to lookup the data in the other list.
The custom field control can be the one to "view" the related data.
I know we have done it for parent child relationships between pages on the same list. Not 1-to-N though.
Tough choice either way.
My vote is "to write this stuff to an external database"
You miss a lot of things in Sharepoint things like transaction support, referential integrity, easy way of updating (compare SQL), reporting (using Reporting Services and a SQL database)... see sharepoint as a way to store documents and simple lists.....
The argument for Sharepoint is if it is a small application, no requirements on support for transactions, no need to import external data etc...
When people say Sharepoint is a development plattform there is a need to define whjat they think a development plattform is.
The latest rumours about Sharepoint 2010 tells us that there will be support for SQL server based lists in next version ..... which I think will at least move Sharepoint in the right direction ....
Take a look at SLAM, SharePoint List Association Manager, an open source project my company created and actively supports. SLAM allows you to synchronize SharePoint data to SQL, including any relationships between lists. SLAM, in addition to being very useful on its own, is really a framework intended to allow developers to create their own complex data associations using what we call SLAM type profiles. We have one out-of-the-box type profile which is part of the open source project which actually allows you to make a SharePoint list hierarchical using the nested set model. For more information, see this page on our codeplex site.
I do this a lot just using sharepoint, using a framework called AAA (Activity,Assignment,Artifact), which allows you to use lookup columns to link an assignment or artifact to a parent Activity. You then build a web part page with connected web parts that allow you to filter all assignments and artifacts by activity. For example, click next to a submission in the submission web part, and all of the submission items attached to that submission will show up. Works great.
The other approach that you can look at using is persisting XML with a field in the item. This is the approach used by the Podcasting Kit (on CodePlex) to store things like ratings.
One possible method is to create a submission content type based on the folder content type and a submission-item based on item content type. Then you can store data hierarchically like in file system and also will work default views and search functionality.
Other way is to create lookup field that points to same list (list=”self”). This field will be used like reference to parent item and you will get list that contains recursively related data. To use this data programmatically will be ok but using views functionality will be little bit complex.
It's easy to do using a connected web part.
Create two lists:
Parent (Id, Title)
Child (Id, Title, ParentId)
Create a new sharepoint page, add DataFormWebPart (displaying Parent) and another one for Child, set both of them to filter based on a QueryString parameter (use that Parameter to filter Parent.Id, and Child.ParentId) voila, you can display parent-child relationships. Now, adding children is more difficult, and that's the part I haven't worked out yet.