bcgov / bcgov/foi-flow

Can type in a past date into Divisional Stage Due date input field and system allows to save

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

Description

**Describe the bug in current situation**
As per the User store for Divisional stage due date(#1674) , system should not allow user to input an old or past due date. But within the current system, if user "type in" an old date, system accepts the past date to save. This behavior can happen with any other date picker with date selection restriction.

Note : From the date picker, it restricts the past date selection. But user can type in - thoughts?

**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. Login as a Ministry user, Go to a request to add DIV. stages with Due date
2. Type in a past date like "01/02/2001"
3. Save the request
4. System saves an past div stage due date.

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

![image.png](https://images.zenhubusercontent.com/607de5aafedfab08839427c4/57b0e66d-9ab5-418b-a5b4-4bdf17d32f06)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the Ministry-user request flow for adding a DIV stage, using a typed past date such as 01/02/2001 rather than the date picker. Trace the save and validation entry points for the Divisional stage due date, then verify that typed past dates are rejected while valid future dates still save; the issue names no files or tests to run.

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
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.