LCFS - Reset Early Issuance Org Permission to "No" After Q4 Submission
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 87
Description
**Describe the task**
Automatically reset an organization’s Early Issuance permission to "No" once they submit their Q4 compliance report. This ensures that organizations must reapply for early issuance annually and demonstrate eligibility under current legislative conditions.
**Purpose**
To enforce compliance with the legislative requirement that early issuance approval must be re-evaluated each year. This prevents assumptions that past approval guarantees future eligibility and ensures consistent application of policy.
**Acceptance Criteria**
- [ ] Upon submission of a Q4 report, the Early Issuance flag for that organization is automatically set to "No".
- [ ] The change is logged and traceable for audit purposes.
- [ ] Ensure this logic only triggers for Q4 submissions (not drafts or other quarters).
- [ ] Confirm that organizations cannot receive early issuance in the new year unless the flag is re-approved manually or through the appropriate process.
-
**Additional context**
- Verify where Early Issuance permissions are stored and how they are applied across the compliance system.
- Consider adding a user-facing message in the system to clarify why early issuance has been reset.
Contributor guide
Research direction
Start by tracing the compliance report submission flow and locating where the Early Issuance permission and audit logging are handled. Verify the behavior for Q4 submissions versus drafts and other quarters, then confirm that the flag resets to "No", the change is traceable, and reapproval is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100