Actions
Bug #10216
closedShow report events in natural order
Description
Displaying a report show events in reverse order (most recent at the top).
I find this confusing because :
I find this confusing because :
- this is the exact opposite order of how events are logged when you simply call
puppet agent --test
- when looking at a failed report, most of the info displayed at the top are 'skipped' classes or resources. This leads to a bad user experience, having to scroll to the bottom of the page in order to find where something went wrong.
If changing the default display order is out of the question (considering some of the users may be used to this display order), how about adding an option to set the default report display order ?
Updated by Dominic Cleal almost 10 years ago
- Tracker changed from Feature to Bug
I think this is an accident, there's no explicit ordering made as far as I can tell - it should be oldest first, to match the tool output.
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2513 added
- Pull request deleted (
)
Updated by Ohad Levy over 9 years ago
- Related to Tracker #10998: Reports UX improvment tracker added
Updated by Dominic Cleal over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 671b0b4409e2ac732613ad2af5d4cd4432f39333.
Updated by Dominic Cleal over 9 years ago
- Translation missing: en.field_release set to 35
Actions