-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trial Session View: NOTT Reminder #9969
Comments
Test Cases1) Petitions Clerk accesses the Open Trial Sessions page; Calendared trial sessions that are between 30-35 calendar days from the scheduled session have a new clock icon next to the date.
Expected Results:
*Repeat this test with a CSS and CotC user 2) Petitions Clerk opens one of the trial sessions that has a new clock icon; new yellow warning banner is present underneath the Session Information header.
Expected Results:
*Repeat this test with a CSS and CotC user 3) Clerk clicks the "Yes, served" link in the yellow warning banner; pop-up modal displays asking for confirmation.
Expected Results:
*Repeat this test with a CSS and CotC user 4) Clerk cancels out of the pop-up modal; clerk is navigated back to the Session information page for the trial session.
Expected Results:
*Repeat this test with a CSS and CotC user 5) Clerk selects "Yes" in the pop-up modal; Yellow warning banner disappears, clock icon is no longer displayed on the Trial Sessions page.
Expected Results:
*Repeat this test with a CSS and CotC user 6) Other Court Staff are able to see the 30 day notice warning banner and clock icon, but are unable to clear the yellow warning banner from view.
Expected Results:
*Be sure to repeat this with all of the other court roles (besides Petitions clerk, CSS, or CotC) to ensure that the warning banner is not dismissible 7) Petitions Clerk sets a calendar, schedules the start date to 36 days from today; The following day, as the Petitions clerk, check the Trial Sessions page; New clock icon and warning banner are present.This test case has some set up:
The next day...
Expected Results:
*Repeat this test with a CSS and CotC User 8) Petitions Clerk sets a calendar, schedules the start date to 30 days from today; The clock icon and yellow warning banner are present.
Expected Results:
*Repeat this test with a CSS and CotC User 9) Petitions Clerk sees the clock icon and yellow warning banner for a session that is 30 days from today; The following day the clerk views the same session; Clock icon and yellow warning banner are no longer present.This test case has some set up:
The next day...
Expected Results:
*Repeat this test with a CSS and CotC User |
Chatted with Mrinalini, we decided alert will use current default width so text will be a single line. (Mocks show double and a custom width so ignore that part.) |
Adding myself to this in case anything else is needed to push it over the line while Mrinalini will be out of office in the next few days. |
@rosiehsmith @mrinsin all tests pass. Thank you! |
Documenting a couple clarifications based on review:
|
As a petitions clerk, so that I can easily see when NOTT notices should be issued, I need an indicator on the trial session view that tells me when the date to issue a NOTT is imminent.
The Court will begin generating and issuing a new Notice of Trial 30 days prior to a pro se petitioner's scheduled trial session. To accommodate this, we would like these notices to have a unique event code on the docket record and the capability to enter as such on the record.
In order to accommodate the time required for paper service and those NOTTs that will be manually docketed, we would like a signifier 5 days prior to the date when the NOTT should be issued. The signifier should be visible on the trial session view and the session detail screen, and should be able to be manually dismissed/cleared by a clerk.
Pre-Conditions
Acceptance Criteria
Notes
Tasks
Test Cases
Story Definition of Ready (updated on 12/23/22)
The following criteria must be met in order for the user story to be picked up by the Flexion development team.
The user story must:
Process:
Flexion developers and designers will test if the story meets acceptance criteria and test cases in Flexion dev and staging environments (“standard testing”). If additional acceptance criteria or testing scenarios are discovered while the story is in progress, a new story should be created, added to the backlog and prioritized by the product owner.
Definition of Done (Updated 5-19-22)
Product Owner
UX
Engineering
test
environment if prod-like data is required. Otherwise deployed to anyexperimental
environment.staging
environment.The text was updated successfully, but these errors were encountered: