Redmine

Forgot to mention, this was an upgrade from 0.8.3 where I followed all documented upgrade steps.

Update on how this appears to work. The grouping appears to be related to the number of issues that you select to appear on each page. For example, if you have 250 total open defects, then grouping by Tracker will never show anything but defects because the first 100 issues are defects. Now, if you scroll to a page beyond 250, then you will see your other Tracker types. Assuming you are showing 100 issues on each page, you will see a non-defect grouping on page 4. By the way, this appears to work the same way with all groupings whether they are seeded values or custom fields.

If my understanding of how grouping works is correct (i.e. that it is dependent upon the number of records selected to be displayed in the GUI), then its usefulness seems diminished. Maybe as a workaround, a "show all records" selection could be added. For my users, I think the expectation will be that grouping will group and display all records that have been filtered, not group the records as they are returned on screen (25, 50, or 100 per screen). I'd appreciate any thoughts or feedback on this as it is entirely possible that I am missing something.

You're not missing anything, but the pagination stuff is there to prevent DOS/too much load on the server, and a "show" all setting will not happen. Regarding the grouping, it's purely a client-side as far as UI goes, so it follows the pagination rules too. I've found it most useful for stuff that breaks the list down into small groups, not into bigger groups like per tracker. For stuff that only makes large groups, the custom queries are much more useful (only show tracker1, tracker2, and so on).