BUG: Unable to update the Requested place for trial when case status is "General Docket - At Issue (Ready for Trial)"

[ttlenard]

Describe the Bug A clear and concise description of what the bug is. When a case is in the status of "General Docket - At Issue (Ready for Trial), and the requested place of trial is empty, court users are unable to add data to the Requested place for Trial. If this scenario happens, a 400 error occurs. (See Screen shot)

Note: if there is already a requested place of trial, and it get's updated, no error occurs. This ONLY happens when the requested place of trial is empty at first.

Business Impact/Reason for Severity

Medium - I found a work-around (see step 8 below)

In which environment did you see this bug? PROD, TEST, MIG

Who were you logged in as? DocketClerk1

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.) Jessica found this in PROD - Using the application

To Reproduce Steps to reproduce the behavior:

1. Be sure you have a case that does not have a requested place for Trial indicated
2. Ensure that the case status is General Docket - At Issue (Ready for Trial)
3. Click on the Case information tab
4. Click on the Edit link next to case details
5. Add in a requested place of trial
6. Click Save
7. Notice that you get a 400 Error.
8. I found a work around for this. Court user can update the case status to ANY Status besides "General Docket - At Issue (Ready for Trial), the court user can then add in the requested place for trial, save it, and then go back and update the Case Status back..

Expected Behavior A clear and concise description of what you expected to happen. Court user can update the requested place for trial - regardless of Case Status

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

Court user can not update the requested place for Trial when the case status is General Docket - At Issue (Ready for Trial)

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

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari] Edge
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Cause of Bug, If Known

Process for Logging a Bug:

• Complete the above information
• Add a severity tag (Critical, High Severity, Medium Severity or Low Severity). See below for priority definition.

Severity Definition:

• Critical Defect Blocks entire system's or module’s functionality No workarounds available Testing cannot proceed further without bug being fixed.

• High-severity Defect Affects key functionality of an application There's a workaround, but not obvious or easy App behaves in a way that is strongly different from the one stated in the requirements

• Medium-severity Defect A minor function does not behave in a way stated in the requirements. Workaround is available and easy

• Low-severity Defect Mostly related to an application’s UI Doesn't need a workaround, because it doesn't impact functionality

Definition of Done (Updated 4-14-21)

Product Owner

• [ ] Bug fix has been validated in the Court's test environment

Engineering

• [ ] Automated test scripts have been written
• [ ] Field level and page level validation errors (front-end and server-side) integrated and functioning
• [ ] Verify that language for docket record for internal users and external users is identical
• [ ] New screens have been added to pa11y scripts
• [ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• [ ] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
• [ ] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• [ ] Interactors should validate entities before calling persistence methods
• [ ] Code refactored for clarity and to remove any known technical debt
• [ ] Deployed to the Court's test environment

[ttlenard]

This looks good. No longer seeing the 400 error. Thank you!