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 - LNG end use label correction of wording #1514

Open
4 tasks
Grulin opened this issue Dec 19, 2024 · 0 comments · May be fixed by #1558
Open
4 tasks

LCFS - LNG end use label correction of wording #1514

Grulin opened this issue Dec 19, 2024 · 0 comments · May be fixed by #1558
Assignees
Labels
Compliance Reporting Critical Ticket is critical and top priority Task Work that does not directly impact the user

Comments

@Grulin
Copy link
Collaborator

Grulin commented Dec 19, 2024

Describe the task
Update the wording of the LNG End Use option in the Fuel Supply Section to correct the percentage range. The current option:

"Compression-ignition engine - Marine, with methane slip reduction kit - Operated within 51 to 75% of load range"

should be updated to:
"Compression-ignition engine - Marine, with methane slip reduction kit - Operated within 26 to 75% of load range."

Purpose
To ensure the LNG End Use option reflects the correct operational percentage range for compliance and reporting accuracy.

Acceptance Criteria

  • Update the LNG End Use option wording to:
    "Compression-ignition engine - Marine, with methane slip reduction kit - Operated within 26 to 75% of load range."
  • Verify that the updated wording appears correctly in the dropdown menu or field where this option is listed.
  • Test the change to confirm that it applies consistently across all user roles (e.g., IDIR and BCeID users).
  • Ensure the updated wording is visible and properly formatted in all reporting sections where the LNG End Use option is referenced.

Additional context
Please ensure no other LNG End Use options are affected by this update.

@Grulin Grulin added Compliance Reporting Critical Ticket is critical and top priority Task Work that does not directly impact the user labels Dec 19, 2024
@kevin-hashimoto kevin-hashimoto self-assigned this Dec 20, 2024
@kevin-hashimoto kevin-hashimoto linked a pull request Dec 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Compliance Reporting Critical Ticket is critical and top priority Task Work that does not directly impact the user
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants