I'm looking at creating a table that could potentially be loaded with 100s of rows. I was hoping to use the growing option that the tables provide. I have a few questions.
If I have a aggregation which is a total for all the rows in that column, will it be the total of all rows or only of those that have been loaded. Or can this be set with a variable etc.
similar to above the select all feature to tick all the rows, will this select every row even the ones not included, or will it just select the loaded rows. Again is this just a variable that I can set.
This is a first time really using any of the UI5 table elements, and the sap said this which I didn't really understand:
"Show Aggregations
Show aggregations (such as totals) on the table footer (sap.m.Column, aggregation: footer).
Do not show aggregations in “growing” mode. It is not clear, if an aggregation will only aggregate the items loaded into the front end, or all items."
For the growing tables, by default all actions and aggregations will only be processed for the data already loaded. Your citation from SAP means that it is not clear to the end user if the aggregated data refers to the visible data or to all data.
If you want to implement something like "Select all" or "Delete All", it would be better to implement this in the backend. From the guidelines of sap.m.List:
In multiple selection mode, users can (de)select all items using the shortcut CTRL+A. This only affects items that have already been loaded to the front-end server. All other items are not (de)selected before they are loaded (for example, items added via lazy loading with growingScrollToLoad). This conflicts with the guideline that all items the user can reach by scrolling must be (de)selected.
To process all items, listen to the selectionChange event and to its flag selectAll. This indicates whether CTRL+A was triggered. As soon as an action is triggered, process the items accordingly. Depending on the number of items, consider processing them in the back end.
Related
The Backlog View allows the user to expand (or collapse) one level of the work item hierarchy at a time - the more times you click the plus, the more levels are revealed. The Query Results view, however, only expands or contracts everything (i.e. all levels at once) no matter how many levels are in your query.
Is there a way to configure a Query View (or all query views is an OK solution too) to work like the Backlogs View?
When I want to list all the items in a Collection in my profile on the MongoDB website, it usually displays just one item and writes something like QUERY RESULTS 5-5 OF MANY above it (although there are 10 items in it), so I have to use arrows to cycle through the items. It's slowing me down when I want to change something about all the items, like maybe add a parameter or change the values.
Is there a way to get rid of that and see more items at the same time, listed in a column so I can edit them faster?
We've come across a number of issues with our Azure DevOps projects and are trying to surface relevant information to the management team with queries and dashboards on projects. Mainly it's just been counting the number of results for particular queries, e.g. when a status hasn't changed in 30 days, number of blocked items, total items in current sprint etc.
What we've been asked for though is to be able to rollup the original estimate total for all work items, and also roll up the completed work as another value. The queries and other things I've seen only seem to be able to count, rather than sum up, but some of the widgets I've seen do appear to sum things for graphs (but I'm just looking for the values).
Can anyone suggest anything?
I imagine that you have two different options here. The first being is that you could leverage the new roll-up columns and aggregate some of this information on the backlog view. Some of this makes assumptions about how you are grouping and the hierarchy of your work items.
Add a rollup column
In the Column options dialog, choose Add a rollup column, select From quick list, and then choose from one of the options listed.
Choose from the menu provided.
Progress bar displays progress bars based on the percentage of associated descendant work items which have been completed or closed.
Total number displays the sum of descendant items or the associated fields of descendant items. Totals provide a measure of the
size of a Feature or Epic based on the number of its child items. For
example, Count of Tasks shows the sum of all tasks that are linked
to parent items. The active or closed state is ignored. Rollup column
menu
Remaining Work of Tasks shows the sum of Remaining Work of tasks that are linked to the parent item.
If you wanted to instead see the summarized details on a dashboard, I'd recommend downloading the Query Tile PRO marketplace extension. Let's say you had a query already defined:
The options support sums based on query fields:
And so you have the tile with the summation value you are wanting. Just replace with other fields that you might need.
When, in Azure Devops, opening the Boards > Backlog page there is no possibility to have an overview of all work items accross all of the teams.
You see "All backlogs", but they are divided into the teams.
I want to see an overview of all work items for all these teams.
Is this possible?
You can just create a simple query:
Then you can format it as a flat list or tree.
But keep in mind that the limit for query results is 20000 items.
I want to see an overview of all work items for all these teams.
You can't do that using any of the regular azure boards (kanban board and sprint board).
The only way (well, the only way known to me) to do that is with Queries (Boards -> Queries). To see work items across projects, remember to check the Query across projects checkbox.
At your disposal you have myriads of fields that you can use to filter your results as well. Use them to fine tune your query result if you want. Last but not least, use Column options to specify which columns to show in your result. Since you want work items across projects, you may want to be able to see which project an item belongs to without opening the item. To do that, include the column Area path from Column options dialog. I use the following columns, and sort by ID descending.
Finally save the query.
Now go to Dashboard, click the Edit button, and add the Query Results widget. Configure that widget to use the query you just created. Note that by default, the column Area Path is not included in the Selected columns list on the right, but you have to include it yourself from the Available columns list on the left. Move columns up/down as you see fit.
Click Done editing when you are done. Through that widget you can edit the work items by clicking on the Title of each work item, which will open the item in a modal. You cannot reorder items (I suppose to set priority) on this widget itself, but hey, setting priority is just a few clicks away, so not a big deal. If you like, you can sort the query result using Priority, and after updating priority you should click Refresh to see the updated result.
Hope that helps!
I have to create a report where main thing is a list of items. On the first page there is also supposed to be a bunch of tables that show figures counted from the list (things like amounts of different types of items etc).
Here is an example to demonstrate the idea. List of the items is actually quite long and goes for multiple pages. Other statistics will be listed only on the front page.
(..edit: seems I can't post images yet..)
I have a database query that retrieves the data for the item list. The question is: Is there a way to use this single query to form all the needed statistics?
All the statistics are such that they can be formed with for example using jaspers groups and variables. I also know how to achieve the desired result by using a subreport for each table (and then I'd even be able tailor the query for each table to directly result the wanted values) but I would like to avoid running the same (or almost same) query for multiple times.
Try to put your table component into the SUMMARY band because detail band repeats the record for every row in dataset.
See this