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

Document-level message thread in document detail #359

Closed
18 of 19 tasks
mariahkannenberg opened this issue Dec 13, 2018 · 1 comment
Closed
18 of 19 tasks

Document-level message thread in document detail #359

mariahkannenberg opened this issue Dec 13, 2018 · 1 comment

Comments

@mariahkannenberg
Copy link

mariahkannenberg commented Dec 13, 2018

As a court user, so that I can be aware of all current and past communication pertaining to a particular document within a case, I need a way to easily see all messages threads associated with that document.

A court user may need to look at the history of all messages on a document. As a result, the user should be able to easily see all threads on a document (open and closed), and be able to navigate through them.

Pre-Conditions

  • User has access to a document in the system

Acceptance Criteria

  • User can view all message threads (pending and closed/completed) associated with a document
  • User can view who closed the final message

Research/Analysis Notes

  • When a message thread is closed, it should add an automatic message that says "Closed by [user name] on [date/time]"

Tasks

  • Design display of completed message threads (Kristen)
  • Create tabs for Complete messages (William)
  • implement view for completed messages (Cody)
  • Implement automated message when message thread is completed, rename properties on messages (Cody)
  • add the check fa-icon on the completed message and also verify the styles match the UX designs (cody)
  • verify design matches UX proof
  • Panel should be fixed height and scrollable (Rachael)
  • If user entered optional message text when completing the message thread, display message. If no message text was entered, do not display any message.

Definition of Done

  • Product Owner
    • acceptance criteria have been met
  • UX
    • [ x] 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 changed the title Document level message thread in document detail Document-level message thread in document detail Dec 13, 2018
@mariahkannenberg mariahkannenberg added the (2) DD Workflow - Petition Epic 2: Document Driven Workflow (Petition) label Jan 11, 2019
@klohman klohman 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 5, 2019

Document Detail

Complete Messages Tab

Under the Messages tab, there is a "Complete" secondary tab that will include all of the completed message threads related to that document

image.png

  • When completed, each message thread will include an automated message of
    "Closed by [username] Date time" (see design mockup)
  • Message history for each message thread will be displayed in reverse chronological order
  • Message threads will be displayed in reverse chronological order
  • Panel should be fixed height and scrollable
  • If user entered optional message text when completing the message thread, display message. If no message text was entered, do not display any message.

@tjcurington tjcurington added this to the Sprint #10 milestone Mar 7, 2019
@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 8, 2019
@tjcurington tjcurington 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 11, 2019
@JessicaMarine JessicaMarine removed the Engineering Engineers have started working on this story. label Mar 17, 2019
This was referenced Mar 19, 2019
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

5 participants