Skip to content
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

Messaging Re-design clean up - Remove old messaging flow #5511

Closed
42 of 46 tasks
JessicaMarine opened this issue Jun 16, 2020 · 3 comments
Closed
42 of 46 tasks

Messaging Re-design clean up - Remove old messaging flow #5511

JessicaMarine opened this issue Jun 16, 2020 · 3 comments

Comments

@JessicaMarine
Copy link

JessicaMarine commented Jun 16, 2020

As a development team, in order to maintain a clean code base and ensure the changes we made to the messaging flow work, we need to remove all of the old messaging flow items that are not used for the new flow and run E2E tests on the new flow.

Pre-Conditions

Acceptance Criteria

  • Disable old messaging flow
  • Test new messaging flow - E2E
  • Remove "Messages" tab from Document QC pages, as well as any other UI remnants from the old flow
  • Old document detail page is removed
  • Once we remove "Messages" from the global header, we need to rename "Case Messages" to "Messages" and make sure everything is renamed correctly on the back end.

Mobile Design/Considerations

Security Considerations

  • Does this work make you nervous about privacy or security?
  • Does this work make major changes to the system?
  • Does this work implement new authentication or security controls?
  • Does this work create new methods of authentication, modify existing security controls, or explicitly implement any security or privacy features?

Notes

Tasks

Definition of Done (Updated 7-2-20)

Product Owner

  • Acceptance criteria have been met
    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)

Engineering

  • Automated test scripts have been written
  • Field level and page level validation errors (front-end and server-side) integrated and functioning
  • Paired w/Mark on data migration work (if applicable)
  • 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)
  • Module dependencies are up-to-date and are at the latest resolvable version (npm update)
  • Errors in Sonarcloud are fixed https://sonarcloud.io/organizations/flexion-github/projects
  • Lambdas include CloudWatch logging of users, inputs and outputs
  • Code refactored for clarity and to remove any known technical debt
  • Rebuild entity documentation
  • Acceptance criteria for the story has been met
  • Deployed to the dev environment
  • Deployed to the stage environment
@mariahkannenberg mariahkannenberg changed the title Messaging Re-design: Clean-Up Messaging Re-design clean up - Remove old messaging flow Jul 10, 2020
@mariahkannenberg mariahkannenberg added this to the Sprint 45 milestone Jul 15, 2020
@klohman
Copy link

klohman commented Jul 17, 2020

Tests

@klohman klohman added the Ready for Engineering UX work is done and this story is ready for engineering. label Jul 17, 2020
@JessicaMarine JessicaMarine modified the milestones: Sprint 45, Sprint 46 Jul 29, 2020
@rachaelparris rachaelparris added Engineering Engineers have started working on this story. and removed Ready for Engineering UX work is done and this story is ready for engineering. labels Jul 30, 2020
@klohman
Copy link

klohman commented Aug 3, 2020

Notes from Jessica (for testing).

(1) I don't think the Recent Messages on the Judge's dashboard is working as expected. I thought it was supposed to show the 5 most recent messages. Check out Judge Buch's -- it's not showing the 5 most recent and they aren't in newest-to-oldest order. (2) Also, in general, there is a lag in messages being added and removed from the Recent Messages on the Judge's dashboard. In staging, a DocketClerk1 sent a Proposed Stipulated Decision to jasford. That message wasn't displaying on the dashboard when I signed in as Judge Ashford. I had to click around a bit before it showed up. Then, when Judge Ashford replied to the message, it stayed on the Recent messages until I clicked around a bit again. (3) Also, when a Docket Clerk completes a message, it's not clearing it from the Inbox until you click around a bit. All of this messaging behavior has to work as expected.

@mrinsin
Copy link

mrinsin commented Aug 3, 2020

(Kristen's findings)

(Mrinalini's Findings)

@JessicaMarine JessicaMarine removed the Engineering Engineers have started working on this story. label Aug 6, 2020
nechama-krigsman pushed a commit that referenced this issue Nov 6, 2024
…te-branch-to-test-1730747568

10461 Story: Public Trial Session Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants