Stop limiting rows to default of 100, it is IRRITATING

[#1]

One of the most irritating issues in Workfront over the years that I have used it is the default display rows are set to 100.

Very often you start analyzing data in either a project task list or a report and much later realizes that you are not looking at ALL the data.

Could the default displayed rows become a feature where each customer can decided how to set the amount or can you at least make the default displayed rows more than 100? If the latter, I would at least suggest 1000 rows.

[#2]

AGREED! I need to see all data. Not scroll all the way to the bottom of the screen to see the record count, change it and reload the report again.

[#3]

We should be able in the reporting feature, or in the dashboard function to set what the default is.

[#4]

There are a couple of those little setting flaws around the system. It is pretty clear that the product team of Workfront is NOT using the system on a daily basis and that the focus is NOT on UX. Instead the product team appears to develop in their own circles and keeping their blind spots. And requests like this one are constantly being ignored and hang around in the system for years. Time for a revolution, not an evolution.

[#5]

We did update this a while ago to default to 2,000 rows, https://one.workfront.com/s/document-item?bundleId=the-new-workfront-experience&topicId=Content%2FWo.... That being said as we update Reporting I am curious what the reason behind wanting to see more rows at once is, is it because the count number changes depending on the number of rows?

[#6]

Hello Matt,

In addition to the count, the custom field data when aggregated(sum, avg, etc) does not give the right picture, as contributions to these custom fields from many other objects are not even shown if they are beyond the specified limit.

[#7]

Hi Matt, this may expand on the topic somewhat, but our biggest issue isn't that the number of rows of detail is limited in the initial view (talking especially about a report in a dashboard), its that whatever you have built into the grouping header for the report (which is often the reason you built the report in the first place) -- be it an average, or a sum, or whatever it might be -- only takes into account the visible rows, not all the data for the report.

We have to explain and remind our users over and over that the initial values they see when the report displays are not meaningful until they See More or click on the report name. So they wait for the initial dashboard load, get results that don't represent what the report is for, and then have to take another step to load the full report and only then get good info.

Again, that may be specific to dashboards vs exactly what you're asking, but thought I'd throw that in there!