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

Add a note to a docket entry #1114

Open
21 tasks
governmentSponsored opened this issue Jan 6, 2025 · 0 comments
Open
21 tasks

Add a note to a docket entry #1114

governmentSponsored opened this issue Jan 6, 2025 · 0 comments

Comments

@governmentSponsored
Copy link
Contributor

governmentSponsored commented Jan 6, 2025

User Story:

As an attorney, in order to capture my impressions of a docket entry, I want to add a note to a docket entry.

Preconditions:

Precondition 1

Acceptance Criteria:

  • The user is able to add a note to the docket entry that includes the pleading
  • The user identity is retained with the note.
  • A date timestamp is retained with the note.

Notes:

First Note

Definition of Done:

  • Acceptance criteria met - The system meets all acceptance criteria
  • Feature toggles created - Features that are deployed but not released have toggles
  • Design QA passed - All visual UI looks and works the way it’s supposed to
  • Usability validated - Team ensures the working code is easy to use
  • Accessibility tests passed - System passes automated and manual accessibility tests and supports applicable devices
  • Code refactored for clarity - Developers can understand the work simply by reviewing the code
  • Dependency Rule followed - More important code doesn’t directly depend on less important code
  • Development debt eliminated - UX and code aligns to the team’s latest understanding of the domain
  • Source code merged - Code has been merged into the main branch
  • 90% unit test coverage achieved - Automated test coverage tools indicate coverage of >= 90%
  • Code reviewed - Code is reviewed by at least two other team members before being merged
  • Code quality checks passed - Code passes all automated quality checks
  • Security scans passed - Code passes expected scans for vulnerabilities and compliance issues
  • Threat model updated - The threat model incorporates new threats and remediations 
  • Build process updated - Automated build process include code supporting the user story
  • Load/performance tests passed - Performance tests include the functionality of the user story
  • Documents are updated - All required documentation is up to date and version controlled
  • Code is deployed - Code is deployed to the highest production like environment
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

1 participant