You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
global errors in the header. clicking on the red box will open an overlay and show all the global errors and warnings.
Placement of pipeline errors notification.clicking on the red circle will open an overlay and show all the pipeline errors and warnings.
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.
The text was updated successfully, but these errors were encountered:
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).
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.
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.
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.
The text was updated successfully, but these errors were encountered: