While we continue to be impressed with how our customers are able to find new ways to use Jama, we strongly discourage making changes directly to configuration files. At this time, we can only ensure system effectiveness with standard settings. While we are not aware of any immediate impact, changes have not been tested and we can not guarantee Jama will not be impacted negatively. Making changes to the configuration files may cause issues that cannot be seen immediately or by all users. There is risk that Jama will become unavailable for all users when needed. We are currently working to provide a longer term solution that will provide greater flexibility around how many items are viewable within the list view. Thanks for the understanding.
Joining this thread late...
Taking away features that users rely on is always a game of Russian-roulette. Early feedback from two of my users is along the lines of "you gotta be --- kidding" and "what are they thinking!!?". I'm afraid I agree.
In the 2014 version, I've had this feature set to 3000 items for my 2800-ish specifications for years, aware that I can improve performance by reducing it, but preferring to sort and scroll as I scan for data errors (a very useful method for detecting anomalies). I'll need to reinvent proxies for this functionality now (export to a spreadsheet?).
I can't picture paging to do what I need to do.
Telling users to write better filters is generally poor UI practice. Sometimes, I don't want a little window into my world; I want to a big one.
Our users would also benefit from being able to see more than 50 items in a view.
Our organization can also benefit from this enhancement as we often have to go back to users and remind them to click on next page and approve as well. An increased limit will reduce the effort spent to complete the review and approval process. Instead of defaulting the # requirements on each page to 50, can we set this to the maximum (500)?
HEADQUARTERS|135 SW Taylor Suite 200, Portland, Oregon, 97204