As an operator,
Given that I have emitted over my emissions threshold,
When I submit my report by May 31,
Then a compliance obligation is generated, with a unique compliance ID
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:
Once an operator has submitted their report
Acceptance Criteria:
As an operator, Given that I have emitted over my emissions threshold, When I submit my report by May 31, Then a compliance obligation is generated, with a unique compliance ID
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:
-