Closed cholly75 closed 4 days ago
UX Notes:
Known issues:
Expected Results:
Part 1
Expected Results:
*Repeat this test but instead choose Remote
Part 2
Expected Results:
*Repeat this test, but add in additional filters for Location and Judge
Expected Results:
Repeat this test by removing multiple filters by clicking on the x in the pill container. Results list will update each time a filter is removed. If you add a new filter to the list, you must click apply filters for the new filter added to "take"
Internal view icon:
Public view icon:
[x]
[x]
[x]
Items flagged by WAVE Evaluation Tool and manual testing:
[x] There is more spacing than previous between the pill and the filter, which impacts the spacing when the browser window width is reduced
[x] Remote proceedings links should open in the same tab
[x] Remote proceedings card should be positioned above the filters (instead of below) when the browser window width is reduced, like it is in mobile view
[x] Mobile - add "Week of" in header row before the date
Some initial Testing feedback: @cruzjone-flexion @nechama-krigsman
Testing Feedback @cruzjone-flexion @nechama-krigsman
Everything looks good, with the exception of the swing session icon not being able to be clicked/hovered on mobile. @swongCO mentioned that there is a design debt card to address this. Once I have the story number for that Design Debt item, I will add it to this comment
UPDATE: Design Debt ticket is #10548
As a member of the public, so that I can easily see what trial sessions are upcoming, I need a public view of the calendared Trial Sessions.
Currently, the Court maintains a web page populated with PDF files to inform the public of scheduled trial sessions. Since this information can become outdated over time and require re-publishing new files when a change is made and since the Trial Sessions in DAWSON are always up to date, we would like a public-facing version of the Trial Sessions page to be made available in place of the current web page.
Note that this story and #10461 should be released together; a feature flag may be necessary to facilitate separate deployments for each.
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
efcms-local.json
, 3 local s3 files corresponding to that docketEntryId have been added toweb-api/storage/fixtures/s3/noop-documents-local-us-east-1
test
environment if prod-like data is required. Otherwise deployed to anyexperimental
environment.staging
environment.