BUG: The "submitted date" changes to today's date when a petitions clerk is Reviewing Petitions that have been submitted electronically

[ttlenard]

Describe the Bug
A clear and concise description of what the bug is.
The submitted date on an electronically submitted petition represents the date it was submitted, until a petitions clerk reviews the electronically submitted petition. Once they review it, the submitted date will change to today's date. (The filed date that is on the cover sheet in the actual uploaded document remains the correct date, but the date in DAWSON switches to Today's date once the Petitions clerk goes in to review it. They are unable to edit this field to ensure that the correct date is input.

Question for the Chris- since we are seeing that the submitted date is whenever the petitions clerk reviews it, and NOT the actual submitted date from the petitioner...how important is this data field to have this info correct? This most likely happened to all eFiled petitions? Not sure how we could get the correct date back in there - it is on the cover sheet of the actual petition...is this stored anywhere else?

Business Impact/Reason for Severity
med severity???

In which environment did you see this bug?
PROD/MIG

Who were you logged in as?
Petitions Clerk

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
This was reported from a court Petitions Clerk

To Reproduce
Steps to reproduce the behavior:

1. Log in as a petitions clerk
2. go to the Section Document QC tab and find a petition that was electronically submitted that needs QC
3. Open the petition and click on the case info tab.
4. Notice the Date received date. For my example, it was back in May 2021. Also notice the filed date in the document itself.
5. click on Review petition. Notice that the Date Received switched to today's date on the Case Details tile.
6. Click Edit in the Case Details, and it will bring you back to be able to review the petition.
7. Now notice that the Date received show's today's date, and not the date that it showed before. This field is not editable, and you cannot get this date to go back to the date it was submitted.

Expected Behavior
A clear and concise description of what you expected to happen.
Date Received should remain the date that the electronic case was received by the court. Not the date that the petitions clerk reviews it.

Actual Behavior
A clear and concise description of what actually happened.
Once a petitions clerk starts the review of the electronically submitted petition, the date received switches to today's date.

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

Case info tab - notice the date received. Also notice the filed date on the cover sheet in the document itself.

After you click review petition, Notice that the date received changes to today's date in the Case Details tile

If you click edit on the case details tile, it will bring you back to the petition details, but you cannot get the date submitted to go back to the real date. The only pace it is correct is on the cover sheet of the petition.

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

[matthopson]

PR to address bug going forward: ustaxcourt#1602

Migration coming in a separate PR.

[ttlenard]

I just tested this and I am still seeing the Date Received switch over to today's date:

This petition was filed on 6/1:

I was in this record on MIG: https://app.mig.ef-cms.ustaxcourt.gov/case-detail/9368-21/documents/5034dd2d-47e4-4646-b645-8d4b6b867474/review

[matthopson]

@ttlenard This isn't on MIG. AFAIK, this fix is only on the test environment.

[ttlenard]

FACE SLAP. I will retest on TEST...ahh geez...

[ttlenard]

This looks great on TEST. Thank you Matt!! (and sorry for my mishap with the environments)