bcgov / bcgov/entity

As a user, I want to see more helptext when I cancel an examined NR, so that I don't expect a refund and get upset

Open
#10,218 0 comments 0 reactions 0 assignees View on GitHub
Client/Staff Feedback ENTITY - DO NOT USE Name Request Priority2
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

### Description
Currently clients are getting upset and calling staff because they cancelled their NR (that had already been examined) and are expecting a refund.
When the NR has NOT been examined, the button says "CANCEL AND REFUND"
When the NR HAS been examined, the button says "CANCEL". It seems that this is not enough, and Debbie would like us to add messaging explaining explicitly that clients will not receive refunds for examined NRs.

### AC

GIVEN I have a name request
AND the name request has been examined (Approved, Rejected, Conditional)
WHEN the client goes to view their existing NR
AND they click "CANCEL"
THEN the client sees more help text on the confirmation modal:

> **The fee for this name request will not be refunded because it has already been examined by BC Registries.**
> The requested name choices will become available to be requested by other businesses.

### Reference
This is the modal that needs updating.
![image.png](https://images.zenhubusercontent.com/5d49cdec9547713e57d6cd4a/03999378-4842-4f79-bbed-cfc3e9f8b589)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the existing name request view and its cancellation confirmation modal, where the CANCEL action is shown for examined requests. Update the modal so examined name requests display the specified no-refund message and the text about name choices becoming available to other businesses. Done means the added help text appears for Approved, Rejected, and Conditional requests without changing the refund wording for unexamined requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.