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

LCFS - New transaction type listing to record compliance report assessments #1668

Open
9 tasks
airinggov opened this issue Jan 11, 2025 · 3 comments
Open
9 tasks
Assignees
Labels
Compliance Reporting High High priority ticket but not critical at this time Story User story Tested w/ issues Testing did not pass

Comments

@airinggov
Copy link
Collaborator

airinggov commented Jan 11, 2025

Description:
Create a new transaction type listing to record compliance report assessments and compliance unit updates on the Transactions index page (both IDIR and BCeID versions).

Wireframe:
(Not included; specify if a wireframe is needed.)

Purpose and benefit to user:
The new transaction type will provide a record of compliance report assessments and associated compliance unit updates, enhancing traceability and usability for stakeholders.

Acceptance Criteria:

  • A new transaction type listing is created and linked to the compliance report.
  • Fields on the index are populated as follows:
    • ID: Includes the prefix "CR" followed by the compliance report ID number.
    • Type: Displays the title of the report version, e.g., “Compliance report – Supplemental 3 – Assessment”
    • From: Displays "N/A."
    • To: Displays the supplier name.
    • Units: Shows the net positive or negative compliance unit adjustment from Line 20 (Delta when supplemental) of the Low Carbon Fuel Target Summary.
    • Value per unit: Displays "N/A."
    • Status: Introduces a new status display labeled "Assessed."
    • Last updated date: Shows the date the report was assessed.
  • The new status display "Assessed" is implemented in the system.
  • All fields update dynamically based on the compliance report assessment details.

Development Checklist:

  • Implement backend logic to generate the transaction type listing and populate fields dynamically.
  • Update the UI to display the transaction type listing with the specified fields.
  • Add a status display for "Assessed."
  • Test field population for various compliance report assessments to ensure accuracy.
  • Validate that the listing links correctly to the related compliance report.

Notes:

  • Ensure alignment with the compliance reporting framework to avoid discrepancies.
  • Discuss with stakeholders the potential inclusion of additional fields or adjustments if necessary.
@airinggov airinggov added Compliance Reporting Medium Medium priority Story User story High High priority ticket but not critical at this time and removed Medium Medium priority labels Jan 11, 2025
@dhaselhan dhaselhan self-assigned this Jan 13, 2025
@Grulin
Copy link
Collaborator

Grulin commented Jan 15, 2025

Newly assessed report for Test Org 6 in the dev environment is not showing this new transaction type. The balance for the organization changed, but I don't see the assessment transaction:

Image

@Grulin Grulin added the Tested w/ issues Testing did not pass label Jan 15, 2025
@dhaselhan
Copy link
Collaborator

There was an issue where these new Transaction types were not showing up for BCeID users, this has now been fixed.

@airinggov airinggov added Tested :) Testing passed and removed Tested w/ issues Testing did not pass labels Jan 17, 2025
@Grulin Grulin added Tested w/ issues Testing did not pass and removed Tested :) Testing passed labels Jan 23, 2025
@Grulin
Copy link
Collaborator

Grulin commented Jan 23, 2025

Just tested this on dev using LCFS2 and it did not show an assessed transaction for the organization after, even though it did show a balance change in their total balance. This was a scenario where they would have been issued credits.

@Grulin Grulin reopened this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Compliance Reporting High High priority ticket but not critical at this time Story User story Tested w/ issues Testing did not pass
Projects
None yet
Development

No branches or pull requests

3 participants