bcgov / bcgov/foi-flow

Due Date in Fee Estimate Payment Email Incorrect

Open
#4,612 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
8
Forks
2
Avg merge
14h 34m
Merged PRs (30d)
46

Description

**Describe the bug in current situation**
On FOR-2023-31888, the due date on the fee estimate payment email is not matching the LDD in FOI Mod.

The posted comment _**incorrectly**_ states:
![image](https://github.com/bcgov/foi-flow/assets/117312323/1c4cdc47-f150-40c5-98d3-d2600fcd92ca)

In addition, the email sent to the applicant _**incorrectly**_ indicated the due date is 08/12/2024

However, the LDD on the request (which is correct) is the following:
![image](https://github.com/bcgov/foi-flow/assets/117312323/9d6218b7-5124-4caa-a2c0-1189a52ac803)

This led to the applicant being sent a letter with an incorrect due date. The due date on the letter should have matched the LDD. The analyst has since emailed the applicant with the correction, but this needs investigation.

**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

The payload names no files, tests, or entry points. Start by tracing how the fee estimate payment email obtains its due date and compare that source with the request's LDD; done means the applicant email and letter use the correct LDD.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.