COAM \ Earned Credits - Internal User can review EC request

[NicoleGovvy]

Description:

CAS staff can review details of an EC issuance request before making recommendations and a final decision.

Figma design

Acceptance Criteria:

As a CAS staff member, given that an operator has requested an EC issuance, when they click 'Review EC request' on the compliance obligation grid, then they can view details of the request submitted by the operator on a new page.

• [ ] 'Review Earned Credit request' page displays as a vertical tab, below 'Review [year] Compliance Summary
• [ ] A button called 'View annual emissions report' can be clicked to view the report [opens as a pop-up]
• [ ] Earned Credits heading

Underneath this heading the following is displayed:

• [ ] Number of earned credits requested

• [ ] Date requested

• [ ] Status of issuance

• [ ] BCCR Trading name

• [ ] BCCR holding account number

• [ ] A new heading called 'CAS Analyst'

• [ ] Field - CAS analyst recommendation: radio buttons showing: - [ ]Ready to approve - [ ] Require changes/corrections - [ ] Decline

• [ ] Field - CAS Analyst's comments: a free-text box to enter comments

• [ ] Save button for the analyst to save

• [ ] Once the analyst saves, their IDIR and date/time are saved

• [ ] A new heading called 'CAS Director'

• [ ] Include text that the following comments will be available to the operator to view.

• [ ] Field - CAS Director comments: a free-text box for the director to enter comments. RESTRICTED ACCESS TO CAS_DIRECTOR ROLE ONLY.

Buttons at the bottom of the page: RESTRICTED ACCESS TO CAS_DIRECTOR ROLE ONLY.

• [ ] Approve
• [ ] Decline

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
• [ ] Reviewed and approved by Product Owner

Blocked By/Blocking

Blocked by #62

Notes:

-

[NicoleGovvy]

When the 'decline' button pressed by the director, the request will show up in the operator's Track Status of Issuance as 'declined' (use appropriate status wording), and they will see the information about how to get more info about the decline (email ghgregulator) and how to appeal.

When the 'approve' button is pressed, the request will show up as approved waiting credit issuance to the operator.

When the approve button is pressed, credits will either be automatically issued in BCCR using the API details (ideal scenario), OR a notification will be sent to CAS staff to manually issue the credits in BCCR

[NicoleGovvy]

@NicoleGovvy the above comment needs a new ticket.