Open jamesmarshall24 opened 4 years ago
Thanks James, that's great.
Note that the squares (switches or status icons?) used to show job history also need to be included in this change. They currently show "green top" for success, "red bottom" for failure (of some kind) and "grey" for no execution history. They would also need a new status for project update, inventory update, or service failures.
Thanks again
@trahman73 is this in the current design?
@wenottingham This can be covered by our new PatternFly status labels (mockup below). We can denote error types using the label text itself.
Status label example: https://tower-mockups.testing.ansible.com/patternfly/jobs/jobs-relaunch-dropdown/
@kdelee @shebangbash @mabashian this seems to have been in an indeterminate state. Did this land, or should this be backlogged?
ISSUE TYPE
SUMMARY
Errors resulting in failed Tower services should be discernible in the UI. Currently both playbook failures and failures as a result of AWX/Tower service failures both show a red circle with a white exclamation mark.
A different visual cue or indicator for playbook vs service failures would help administrators prioritize which issues to look into first. We would also like to see specific failures outlined in the cues that are discernible from a top down level.
For example, jobs failed as a result of a project update, inventory update, or service failure should all have different visual cues on the UI. From the "jobs" page, you could then see if the job failed based on one of those three categories by looking at the status marker rather than having to click into each job to verify.