BUG
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 87
Description
**Describe the Bug:**
The **Schedule B fuel supply select list** is not functioning correctly in the **dev environment** and has also been reported as an issue in **production**. Specifically, the **End Use** field for at least one fuel type does not provide any options for selection.
**Expected Behaviour:**
- The **Schedule B fuel supply select list** should display the correct options for all fuel types.
- The **End Use** field should provide appropriate selectable options based on the selected fuel type.
- The functionality should work consistently across **dev** and **production** environments.
**Actual Behaviour:**
- The **fuel supply select list** is **not working properly** in the **dev** environment.
- The issue has also been reported in **production**.
- The **End Use** field for at least one fuel type does not populate any options, preventing selection.
**Implications:**
- Users **cannot** correctly specify fuel supply details in **Schedule B**, potentially leading to incomplete or incorrect compliance reports.
- **Blocking issue** for users relying on the **End Use** selection.
- **Inconsistencies** between environments may indicate a **deployment or configuration issue**.
**Steps To Reproduce:**
1. Navigate to **Schedule B fuel supply** in the **dev** environment.
2. Attempt to select a fuel type and observe if the select list works correctly.
3. Attempt to select an **End Use** for the fuel type.
4. Observe whether options are available for selection.
5. Repeat in **production** to confirm the issue persists.
**Notes:**
- Verify whether the issue affects **specific fuel types** or **all selections**.
- Investigate if **environmental differences** (dev vs prod) are contributing to the issue.
- Confirm whether a **recent deployment or update** impacted the select list functionality.
- Ensure the **End Use options** are correctly mapped and available based on the selected fuel type.
- Test for any **JavaScript errors** or missing API responses in the developer console.
Contributor guide
Research direction
Start by reproducing the Schedule B fuel supply and End Use selection problem in dev, then compare the browser console and network responses with production. Trace the fuel-type-to-End-Use mapping and deployment differences; done means every affected fuel type provides the correct selectable options in both environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- backend, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100