Applying a Fee Wavier in any Request State
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 46
Description
**Describe the bug in current situation**
When a fee waiver needs to be applied to a request, the request must be in the On-Hold state for the value to be entered. In any state besides the On-Hold state, the fee waiver option is greyed out and no information can be entered.
**Link bug to the User Story**
**Impact of this bug**
Fee waivers can be granted at any point during a request's lifecycle. It slows the process down for the IAO analyst and client ministry to constantly move a request back into the On-Hold state to enter this information.
**Chance of Occurring (high/medium/low/very low)**
High
**Pre Conditions: which Env, any pre-requisites or assumptions to execute steps?**
**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to Any request in any state besides On-Hold
2. Click on the CFR tab
3. Scroll down to the fee waiver option
4. See Error
**Actual/ observed behaviour/ results**
The fee waiver box remains grey and the value of the fee waiver cannot be entered by the IAO analyst or ministry client.
**Expected behaviour**
GIVEN An IAO analyst or ministry coordinator is in a request, in any state, where a full or partial fee waiver is granted
WHEN They select the CFR tab on the request
THEN The fee waiver box will be live and editable
AND the value of the fee waiver can be entered.
**Screenshots/ Visual Reference/ Source**
If applicable, add screenshots to help explain your problem. You an use screengrab.
Contributor guide
Research direction
Reproduce the issue by opening a request outside On-Hold, selecting the CFR tab, and checking the fee waiver control. Trace the request-state logic that disables this control and add coverage for editing a full or partial waiver in another request state; done means the field is live and editable without moving the request to On-Hold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100