Project

General

Profile

Feature #5265

Need a consistent way to handle severe server side exceptions in all our UI pages to show the user the error and indicate that something failed

Added by Mike McCune about 6 years ago. Updated 9 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Web UI
Target version:
-
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Currently when a new2pane page has an error submitting a form you often get nothing in response to a post and the user is left guessing why something isn't working. The only way to view the error is to look at production.log.

We need errors to bubble up to the UI in a consistent manner
----
Imported from https://trello.com/c/g6A4jKzP/375-5-need-a-consistent-way-to-handle-severe-server-side-exceptions-in-all-our-ui-pages-to-show-the-user-the-error-and-indicate-that_

History

#1 Updated by Eric Helms almost 6 years ago

  • Category set to Web UI
  • Difficulty set to medium
  • Triaged set to Yes

#2 Updated by Eric Helms almost 6 years ago

  • Subject changed from [5] Need a consistent way to handle severe server side exceptions in all our UI pages to show the user the error and indicate that something failed to Need a consistent way to handle severe server side exceptions in all our UI pages to show the user the error and indicate that something failed
  • translation missing: en.field_story_points set to 5.0

#3 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) set to 86

#4 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 114

#5 Updated by John Mitsch 9 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from New to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF