bcgov / bcgov/entity

NAMEX - Status remains as Refund Requested - Name Requests updates to Refund Request Processed

Open
#14,149 0 comments 0 reactions 0 assignees View on GitHub
bug ENTITY - DO NOT USE
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

**Describe the bug in current situation**
This bug initiated with OPS ticket #1641. Staff noticed that refunds on NRs would complete and the status in NRS would update to Refund Request Processed. In NAMEX, the status would change to Refund Requested but never update to any other value when the refund was complete. There doesn't seem to be any status difference in NAMEX when a refund has been requested, when the refund has been submitted and when the refund is complete.

**Link bug to the User Story**

**Impact of this bug**
Staff must look in NRA to know when a refund is complete.

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

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

**Steps to Reproduce**
Steps to reproduce the behavior:
1. Complete and pay for NR, then approve
2. Cancel NR for refund
3. Check status in NAMEX.

**Actual/ observed behavior/ results**
Status in NAMEX remains at Refund Requested, even when Refund is complete.

**Expected behavior**
Status in NAMEX is updated to reflect that the refund is complete.

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

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the NAMEX refund-status flow using the listed reproduction steps, and trace how a completed refund is represented after cancellation. Compare the NAMEX status with the expected Refund Request Processed state; done means completed refunds no longer remain at Refund Requested.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.