Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pipeline error and global errors #3882

Open
naveenbhaskar opened this issue Sep 21, 2017 · 2 comments
Open

Pipeline error and global errors #3882

naveenbhaskar opened this issue Sep 21, 2017 · 2 comments
Labels
no stalebot Don't mark this stale. ux-enhancement

Comments

@naveenbhaskar
Copy link
Contributor

story : error handling in GOCD

Since all the errors are showing in a single place, the chances are high that important errors and warning miss from users. So moving all the pipeline related errors to pipeline tile and other global errors to the top right part of the header.

  1. global errors in the header. clicking on the red box will open an overlay and show all the global errors and warnings.
  2. Placement of pipeline errors notification.clicking on the red circle will open an overlay and show all the pipeline errors and warnings.

image

image

Both error overlays looks the same in terms of UI.
sections which has a red vertical line on the left are errors and yellow vertical lines are warnings.

@gibsonm
Copy link

gibsonm commented Aug 24, 2018

As an admin, I like the separation, but would still like a single place that notifies me of any pipeline errors. Can we maybe have two separate spaces for warnings along the title bar (one for global, one for pipeline), as well as having the pipeline specific error icons (a great idea btw).

@stale
Copy link

stale bot commented Apr 1, 2020

This issue has been automatically marked as stale because it has not had activity in the last 90 days.
If you can still reproduce this error on the master branch using local development environment or on the latest GoCD Release, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.

@stale stale bot added the stale label Apr 1, 2020
@stale stale bot closed this as completed Apr 8, 2020
@chadlwilson chadlwilson added no stalebot Don't mark this stale. and removed stale labels Mar 9, 2023
@chadlwilson chadlwilson reopened this Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no stalebot Don't mark this stale. ux-enhancement
Projects
None yet
Development

No branches or pull requests

4 participants