flexion / ef-cms

An Electronic Filing / Case Management System.
23 stars 10 forks source link

BUG: Trial Session with a large group of consolidated cases is returning 502 Error #10186

Closed ttlenard closed 1 year ago

ttlenard commented 1 year ago

Describe the Bug A clear and concise description of what the bug is. It was reported to us that a Trial Session was not opening for a Judge/CA. After investigation, this case had a very large group of consolidated cases on the calendar.

Business Impact/Reason for Severity Critical

In which environment did you see this bug? Test and Prod

Who were you logged in as? Any Court User

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.) This was reported to us by a CA

To Reproduce Steps to reproduce the behavior:

  1. Go to this trial session: Atlanta, GA 3/4/24: https://app.test.ef-cms.ustaxcourt.gov/trial-session-detail/9c0bcc28-48c6-48d8-b52d-8d2688fe751c
  2. You will receive a 502 error message

Private Zenhub Image

Private Zenhub Image

Expected Behavior A clear and concise description of what you expected to happen. Trial session page should open

Actual Behavior A clear and concise description of what actually happened. 502 error occurs

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Smartphone (please complete the following information):

Cause of Bug, If Known We believe this is just pulling too much information. It was over 11MB

Process for Logging a Bug:

Severity Definition:

Definition of Ready for Bugs(Created 10-4-21)

Definition used: A failure or flaw in the system which produces an incorrect or undesired result that deviates from the expected result or behavior. (Note: Expected results are use cases that have been documented in past user stories as acceptance criteria and test cases, and do not include strange behavior unrelated to use cases.)

The following criteria must be met in order for the development team to begin work on the bug.

The bug must:

Process: If the unexpected results are new use cases that have been identified, but not yet built, new acceptance criteria and test cases should be captured in a new user story and prioritized by the product owner.

If the Court is not able to reproduce the bug, add the “Unable to reproduce” tag. This will provide visibility into the type of support that may be needed by the Court. In the event that the Court cannot reproduce the bug, the Court will work with Flexion to communicate what type of troubleshooting help may be needed.

Definition of Done (Updated 4-14-21)

Product Owner

Engineering

ttlenard commented 1 year ago

Testing looks good. Thanks all!