Additional Reporting Data Page: Regulated Operations and Reporting-only Operations

[suhafa]

Description:

As a Regulated Operation, I want to add additional data so that I can fill out my emissions and compliance report As a Reporting Operation, I want to add additional data so that I can fill out my emissions report, and need to ensure that "electricity generated" is an optional field only.

This page is required for all Regulated Operations (including Opt-ins and New Entrants) & Reporting Operations. It does NOT apply for EIOs or Simple Reports. The emissions and compliance reports are done at the facility level, but there are a couple of data fields that we need to ask users for at the operation level. For SFOs this won't make a difference, and will just be an additional page after emissions and compliance data. For LFOs they would see this page after they have completed all the facility level emissions and compliance forms.

Wireframe

Acceptance Criteria:

Given that I am a Regulated operation When I've completed all the facility-level reports (emissions and production) Then I need a form to fill in additional information

Given that I am a Reporting Operation When I've completed all the facility-level reports (emissions only) Then I need a form to fill in additional information,

Development Checklist:

• [ ] Add a model report_additional_data to store the additional fields required for Regulated and Reporting Operations. This will track the extra data added at the operation level.
• [ ] Add an additional reporting data page at /reports/{version}/additional-reporting-data
• [ ] Additional reporting data is saved to the report_additional_data table on continue/save
• [ ] Form for capturing emission should be rendered only if user clicks on yes for Did you capture emissions?
• [ ] 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
• [ ] Reviewed and approved by Product Owner

Notes:

• We have separate tickets for the "Additional Data" forms specific to a) New Entrants b) Regulated Partial Year

[patriciarussellCAS]

I took a stab at refining this but need to discuss at next week's refinement with everyone/

[rdromey]

@ayeshmcg to write dev checklist