BUG: Blocked Label is not displaying appropriately when adding or deleting a deadline on a case for users on the West Coast

[ttlenard]

Describe the Bug
A clear and concise description of what the bug is.
While testing #10440, I noticed that the blocked label wasn't displayed in the case header after adding a deadline on a case, and subsequently the case wasn't getting added to the Blocked Cases report. I also noticed that when I deleted the deadline on the case, it was only then that the blocked label displayed. The blocked label should NOT be displayed after the deadline is deleted.

While testing, I noticed that this was happening on Staging as well. We asked a Court user on Production to test it, and they did not see any issue. We then performed another test on the test environment with a user that hits the east coast, and they did not experience the same issue. This led us to believe that this problem is only happening to West Coast users.

Business Impact/Reason for Severity
Medium

In which environment did you see this bug?
Test, Staging (and most likely Production)

Who were you logged in as?
Case Services supervisor, docket clerk

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
Testing #10440

To Reproduce
Steps to reproduce the behavior:

1. Be sure that you hitting the West Coast database
2. Log in as a CSS
3. Navigate to a case with no tracked items that is not Blocked and click on the Create menu
4. Select Deadline
5. Add in a new deadline
6. Click Save and then Refresh your screen (known bug (BUG: The blocked label doesn't appear on the case header after adding a deadline to a case, user must refresh. #10515) that you have to refresh to get the blocked label to display on the header after adding in a deadline.)
7. Notice that the Blocked label does not display in the case header, and the case is not on the Blocked Cases report. The case WILL display on the Deadlines report.
8. Next, delete the deadline.
9. Notice that now that you have deleted the deadline, the Blocked label displays on the header, even though the case shouldn't be blocked. (I had the case JSON up and see that the automatic blocked gets set to True here)
10. There is now no way that a user can remove the blocked label.
11. If you hit the East coast DB, none of this behavior (minus the known bug where you need to refresh) happens.

Expected Behavior
A clear and concise description of what you expected to happen.
West coast and East coast users need to experience the same things, West coast should be able to add in a deadline and have the blocked label display.

Actual Behavior
A clear and concise description of what actually happened.
West coast users can add in a deadline, but the blocked label does not display. Works fine for east coast users

Screenshots
If applicable, add screenshots to help explain your problem.
I added in a deadline, which saved to the case just fine, but the Blocked label is not displayed in the header, and the json data shows automaticBlocked = false.

After I deleted a deadline on this case. Blocked label displays, and see the data in the case json

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• 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 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:

• Be focused on solving a user problem
• Contain data for all fields in the bug template, so the team can pick it up and begin working immediately

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

• 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 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 if prod-like data is required. Otherwise, deployed to any experimental environment for review.

[Mwindo]

This is indeed likely a West Coast vs. East Coast issue. In updateCaseAutomaticBlocked, we query for case deadlines on a case (from the East or West, depending on the client location). However, if we have just inserted or removed case deadlines (a write that happens in the East)--as we do in createCaseDeadline.ts and deleteCaseDeadline.ts--then that update might not appear in the West.

[ttlenard]

Tested with users that would hit both East and West coast and it appears to be fixed now. Thank you!

[ttlenard]

@pixiwyn @Mwindo

Actually, I think I spoke too soon in the above comment. I believe I found another instance where the Blocked Label isn't displaying appropriately for West Coast Users. This has to do with auto-generated Orders in the Petition flow that auto-generate Deadlines, therefore blocking a case.

• Petition is reviewed and the following checkboxes are checked for auto-generating Orders. 1) Order for Filing Fee, Order for amended petition and filing fee, and Order for amended petition.
• Serve the petition to the IRS
• Go back to the document QC processed tab
• Click on the case docket number of the case that you just served
• Click on the draft tab
• Sign one of those orders (we were testing with Order for filing fee)
• Add the order to the docket record
• East coast get's a blocked label/West Coast does not

[ttlenard]

Issues seem to be resolved. Thank you!