bcgov / bcgov/foi-flow

CFR form history has invalid or Zero fee "Estimate values" on VOLUME section

Open
#3,129 0 comments 0 reactions 0 assignees View on GitHub
bug medium priority
Dominant language
Python
Stars
8
Forks
2
Avg merge
14h 34m
Merged PRs (30d)
46

Description

**Describe the bug in current situation**
Create a CFR Fee estimate Form-= Say V1, with estimates on VOLUME section and go for applicant payment . then after payment from applicant , enter actuals. Then observe the CFR History, we can see "Zero" under that section, - actually there were values on fee estimate of VOLUME - but it shows as 0

Version 1 active form value for VOLUME ESTIMATEs

![image.png](https://images.zenhubusercontent.com/607de5aafedfab08839427c4/1bee36f2-627f-4788-aa6d-69020a1e89a7)

Version 1 HISTORY form value for VOLUME ESTIMATEs
![image.png](https://images.zenhubusercontent.com/607de5aafedfab08839427c4/99696085-011d-4abd-8402-5eb78b3c0d65)
**Link bug to the User Story**

**Impact of this bug**
Describe the impact, i.e. what the impact is, and number of users impacted.

**Chance of Occurring (high/medium/low/very low)**

**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**

**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Actual/ observed behaviour/ results**

**Expected behaviour**
A clear and concise description of what you expected to happen. Use the gherking language.

**Screenshots/ Visual Reference/ Source**
If applicable, add screenshots to help explain your problem. You an use screengrab.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by reproducing the CFR fee-estimate flow with VOLUME estimates, then compare the active form values with the CFR History after applicant payment and actuals are entered. Done means the history shows the original VOLUME estimate values instead of zero.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.