Skip to main content

Filter by idea status

10000+ Ideas

AndreyPoLevel 2

Reporting - Aggregator function to cover the entire result set in a report (instead of just the displayed records)New

Currently, when an aggregator function is used to display a calculated total for a particular custom field in a result set, only the the displayed page is included in the calculation. This means that IF the entire data set is 5000 records, the user will see the aggregated total in the grouping headers for the first 100 results or 2000 max (if they figure out how to adjust the default limit). This can be rather confusing to users due to the fact that the user expects the aggregated total to include the entire data and not the default 100 records or at most 2000 records per page. It's particularly problematic when it comes to an Hours report where the result set can include well over 2000 records, meaning that the user has to have their calculator app handy and then paginate through the result set while adding the totals from each page to get the total across the complete data set OR they must export the data set into Excel and continue their calculations there. What we need is an enhancement which would allow users to see the aggregated values in grouping headers for the entire data set (no matter how large that set is) without having to rely on exporting data into Excel.Here's an example of a large data set and what the user sees by default:and here's what they CAN see if they expand the default result set to the max of 2000 records... completely different totals for the same groupings AND there are additional groupings that got added because the displayed data set now includes them... ...even still, there are 1700+ records on the next page that were not included in the total which may have data not aggregated on the displayed page, thus rendering the Total Cost column useless for large data sets unless the user exports the data into Excel.

VernPhLevel 3

Drag and Drop Kanban Stories to Specific LocationNew

When managing stories on an Agile Kanban board and moving a story from one status to the next in a sequence, we need the ability to drop the story in the next status at a certain location within the list of stories. Current functionality is for the story to retain it's comparative position that it had when it was in the backlog.We are a production support organization for a data warehouse and may have a new story come into the backlog that is a higher priority than an existing, in-flight, story. Under current functionality, as the story moves through the release process, the story will be put at the bottom of the list of existing stories (in each status) and we must then manually move the story to the top of the list so it will be worked on next by the Agile team. In another situation, if a backlog story's priority changes and it needs to be expedited, it will be placed in the list of existing stories in the same order it appeared in the backlog. That location is rarely where we now want it listed. We must also find the story in the list and then manually move it to the correct position.We current spend time after nearly every Kanban stand-up reordering the stories so that they reflect the actual priority of work.What we need is the ability to drop the story into a specific location in the list of stories. That position is not related to the position it was on the backlog. Basically, we would like to replicate the manual Post-it notes where a story is inserted into the list of stories already on the board.The current functionality does not compare well with other products who manage Kanban boards.