bcgov / bcgov/entity

UI DESIGN - Include the word "None." in the registration UI to match the verification statements and search result reports

Open
#10,887 0 comments 0 reactions 0 assignees View on GitHub
Assets enhancement Review with Business UX
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

If the user does not enter anything for the description of general collateral when they create their base registrations, the word "None." is displayed (added by the system) in the description of general collateral in verification statements and search result reports.
This is unexpected behaviour, inconsistent with the display of the information in the UI, and is not described to the user. This may confuse some users.
The design of the UI should remove this potential confusion.

**Consider**:
Including text describing the automatic system behaviour
Including "None" on the review step in the GC section of base registrations
Including "None" in Amendments, Renewals, and Discharges

As well if there is no based registration GC it is displayed differently in Amendments than if there is GC entered in a base registration. When there is no GC in the based registration the base registration GC is not indicated in Amendments, but if there is base registration GC the base registration GC is indicated.

This may confuse some users - they may believe that the base registration GC is always indicated and they may wonder why the base registration GC is not displayed.

Amendment No GC
![image.png](https://images.zenhubusercontent.com/5bdb286ef2d4f912cf500d34/6071ccee-29a9-46fa-956c-3a251660118e)

Amendment GC
![image.png](https://images.zenhubusercontent.com/5bdb286ef2d4f912cf500d34/3db19b6f-27e2-4161-bb05-02f0faef1493)

Also the date and time of the base registration GC should be indicated as it is with amendments.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.