execution-list bad sort & no mentioned filter is used
When user open mistral CLI and run mistral execution-list he gets a list of the FIRST 100 executions.
this behavior is not idle and very confusing!
- There is no indication to the user he is getting a filtered list
- User which got to a point he needs debugging will probably do that because of a recent failures and will expect to get the latest execution upon running the command.
(In most cases getting the filtered first executions will render him confused on where are the executions which recently failed)
Really not clear and intuitive to find out how to get more results, or to change the filter sort order to show latest executions.
I believe this is a basic usability that every component should have.
To use the following every time I need to see the latest executions seems to me absurd and messy
mistral execution-list --sort_
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- shahar
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by