Any compliance units (offsets or earned credits) moved from the designated holding to compliance account will be considered to be used against the particular compliance obligation. The API will bring information about the units in the compliance account and reduce the obligation balance.
Acceptance Criteria:
Given
When
Then
Development Checklist:
[ ] Checklist item
[ ] Checklist item
[ ] Checklist item
[ ] Meets the DOD
Definition of Ready (Note: If any of these points are not applicable, mark N/A)
[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)
Definition of Done (Note: If any of these points are not applicable, mark N/A)
[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
Description:
Any compliance units (offsets or earned credits) moved from the designated holding to compliance account will be considered to be used against the particular compliance obligation. The API will bring information about the units in the compliance account and reduce the obligation balance.
Acceptance Criteria:
Given When Then
Development Checklist:
Definition of Ready (Note: If any of these points are not applicable, mark N/A)
Definition of Done (Note: If any of these points are not applicable, mark N/A)
Blocked By/Blocking
Notes:
-