Bug: Review Changes Page displaying incorrect deletion
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
#### Describe the Bug:
User from Kelt BC did screenshare and found the following issue:
1. Created a supplementary report and made an update to their **_small aggregate facility_** (Kelt BC Gas Field) - they changed **the annual fuel amount for GSC non-compression and non-processing combustion**
2. On the review changes page, the annual fuel amount change was displayed properly BUT - it showed that GSC non-compression and non-processing combustion was **deleted** for their **_Large facility_** (Kelt LNG Oak 06-35 MWGEB) which was NOT true.
3. This lead to user confusion. They tried to fix the problem which lead to double counting of emissions.
4. Our solution was to delete the current draft and start a new one. I can confirm that the error on the Review Changes page was still there - though this time we clicked through and the final review page was correct, so they submitted the supplementary report.
#### Probability: 3 - not sure how common this is across users. And if it's just LFOs?
#### Impact: 4 - it led to user trying to add something that wasn't actually deleted and changed their compliance obligation.
#### Screenshots:
#### Additional information:
OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
#### Additional Context
-
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the supplementary-report workflow described in the issue: update the annual fuel amount for GSC non-compression and non-processing combustion on the small aggregate facility, then inspect the Review Changes page for the large facility. Compare its displayed deletion with the final review page; done means the unchanged large-facility item is not shown as deleted and the submitted report remains correct.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100