BUG: Entered and Served Stamp not displayed on Stipulated Decision

[JessicaMarine]

Describe the Bug In 5087-20, the Court entered a Stipulated Decision. The "Entered and Served" date does not appear on the bottom of the 1st page.

Business Impact/Reason for Severity

• There are several legally significant issues tied to that entered and served date -- appeal rights, assessment timing, etc.

In which environment did you see this bug? Court's migration; reproduced in Mig

Who were you logged in as? IRS

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.) Reported by IRS

To Reproduce Steps to reproduce the behavior:

1. Log in to MIG
2. Go to 5087-20
3. Click on the Stipulated Decision (entry #14)
4. Note that no "Entered and Served" date is displayed on the PDF

Expected Behavior

• Entered and Served date must be displayed on the PDF

Actual Behavior

• Entered and Served date is not displayed on the PDF https://app.zenhub.com/files/152320868/e0797e52-2036-4b08-ade5-c62ca48000c5/download

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]
• 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 2-23-21)

Product Owner

• [ ] Acceptance criteria have been met and validated on the Flexion Prod env

UX

• [ ] Business test scenarios to meet all acceptance criteria have been written
• [ ] Usability has been validated
• [ ] Wiki has been updated (if applicable)
• [ ] Story has been tested on a mobile device (for external users only)
• [ ] Add scenario to testing document, if applicable (https://docs.google.com/spreadsheets/d/1FUHKC_YrT-PosaWD5gRVmsDzI1HS_U-8CyMIb-qX9EA/edit?usp=sharing)

Engineering

• [x] Automated test scripts have been written
• [x] Field level and page level validation errors (front-end and server-side) integrated and functioning
• [x] Verify that language for docket record for internal users and external users is identical
• [x] New screens have been added to pa11y scripts
• [x] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• [x] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
• [x] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• [x] Module dependencies are up-to-date and are at the latest resolvable version (npm update)
• [x] Errors in Sonarcloud are fixed https://sonarcloud.io/organizations/flexion-github/projects
• [x] Lambdas include CloudWatch logging of users, inputs and outputs
• [x] Interactors should validate entities before calling persistence methods
• [x] Code refactored for clarity and to remove any known technical debt
• [x] Rebuild entity documentation
• [x] Acceptance criteria for the story has been met
• [ ] Deployed to the dev environment

• [ ] Deployed to the Court's migration environment

  Review Steps

  1. Finish all other DOD
  2. Deploy to the dev environment
  3. Engineers add Needs UX Review label
  4. UX Review on dev environment (if feedback, implement and go back to step 2)
  5. UX add Needs Migration Deploy label
  6. Deploy to the Court's migration environment
  7. Engineers go through test scenarios on Court's migration environment
  8. Engineers add Needs PO Review label and move to Review/QA column
  9. PO review (if feedback, implement and go back to step 2)

[JessicaMarine]

The placement of the signature is moving about an inch upwards on save: