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

Court User: Start a message thread #962

Closed
33 of 34 tasks
tjcurington opened this issue Feb 27, 2019 · 1 comment
Closed
33 of 34 tasks

Court User: Start a message thread #962

tjcurington opened this issue Feb 27, 2019 · 1 comment

Comments

@tjcurington
Copy link

tjcurington commented Feb 27, 2019

As a Court User I need to be able to create a new message that will start a thread, so that I am able to communicate to other internal court users regarding a document within a case

PreCondition:

  • A document exists in the case docket record

Acceptance Criteria

  • The Court User is able to start a new message
  • The Court User is able to choose a message recipient (any internal court user)
  • The Court User is able to free-form a message in the thread
  • The new message is viewable in the docket detail page, the case detail page, in the senders sent box, and in the queue of the recipient
  • The sent message is viewable in the sender's individual and section Sent box [Note: make sure Sent box is built out for all users]

Tasks

Definition of Done

  • Product Owner
    • acceptance criteria have been met
  • UX
    • usability has been validated
  • Engineering
    • Field level and page level validation errors (front-end and server side) integrated and functioning
    • run the browser stack scripts to verify that application is usable in Chrome, Firefox, Safari, Edge and Internet Explorer (external only)
    • No errors reported in manual a11y testing
    • All new functionality verified to work with keyboard and osx voiceover
    • Code refactored for clarity and to remove any known technical debt
    • README, other appropriate docs, and swagger/APIs fully updated - all code functions documented with jsdocs
    • UI should be touch optimized and responsive for external only(functions on supported mobile devices and optimized for screen sizes as required)
    • library/module dependencies are up-to-date and are at the latest resolvable version
    • CI/CD - Code is deployed to DEV
  • Other
    • alerting and monitoring for new functionality in place and successfully exercised
@mariahkannenberg mariahkannenberg added Delay Ship Indefinitely - Yes (2) DD Workflow - Petition Epic 2: Document Driven Workflow (Petition) labels Feb 27, 2019
@uxforgood uxforgood added the Design Needed Design work will be needed and development work should not start yet label Mar 4, 2019
@klohman
Copy link

klohman commented Mar 4, 2019

Document Detail page

Messages Tab

  • Update interface to show secondary tab under "Messages"
  • "In Progress" tab- displays all message threads that are active for a document
  • "Complete" tab- will display completed messages (to be built out in story 359)

image.png

Create Message

  • On click of Create Message button, open Create Message modal:

image.png

  • Select Section dropdown (required)

    • list will include all user sections/roles (docket, petitions, chambers, etc.)
  • Select Recipient dropdown (required)

    • field is disabled until Section has been selected
    • dropdown list is populated with the users within the selected section
  • Message field (required)

New Message thread

  • On click of "Send", if all required fields are complete:
    • Modal closes and page refreshes
    • New message thread is created
    • Message is displayed on the "In Progress" tab on the Document Detail Page
      • "To" displays as the recipient
      • "From displays the user who sent the message
      • "Received" - date/time that the message was received in the recipient's queue

Screen Shot 2019-03-04 at 1.28.19 PM.png

  • New Message is displayed in the recipient's work queue inbox
  • New Message is displayed in the recipient's section work queue inbox
  • New message is displayed on the Case Detail page under "Messages In Progress"

image.png

  • Sent Message is displayed in the sender's work queue "Sent" box and the Section Queue "Sent" box
    - "To" displays as the recipient
    - "From displays the user who sent the message
    - "Sent" - date/time that the message was received in the recipient's queue

Form Validation

  • all fields in the Create Message modal are required
    • On click of "Send", Validate all required fields are complete
    • Display field level errors for incomplete fields

image.png

@klohman klohman added Ready for Engineering UX work is done and this story is ready for engineering. and removed Design Needed Design work will be needed and development work should not start yet labels Mar 4, 2019
@tjcurington tjcurington added this to the Sprint #10 milestone Mar 7, 2019
@ericsorenson ericsorenson 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 Mar 13, 2019
wbyoko added a commit that referenced this issue Mar 15, 2019
wbyoko added a commit that referenced this issue Mar 15, 2019
* Update message text
wbyoko added a commit that referenced this issue Mar 15, 2019
@JessicaMarine JessicaMarine removed the Engineering Engineers have started working on this story. label Mar 17, 2019
This was referenced Mar 19, 2019
rachaelparris pushed a commit that referenced this issue Mar 29, 2021
Latest to Migration (with 5311)
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

7 participants