bcgov / bcgov/entity

UI Design - Removal of Folio from Staff Payment Component - Entity

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

Description

Staff have identified that there are cases where folio should be collected but not within a BCOL payment record (currently staff have routing slip and no-fee). Staff have requested the option to enter folio without it being associated to a BCOL account.

Actions
1. Determine Entities transactions that do not have folio options outside of the staff payment
2. Create designs to add folio outside of staff payment. Note: we should already have folio outside of staff payment for client flows which could be exposed in staff flows

**Grooming and completing this work will require coordination across teams.**

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the existing client-flow folio handling and the staff payment, routing-slip, and no-fee flows. Determine which Entity transactions lack a folio option outside BCOL payment records, then coordinate across teams on designs that expose the existing client-flow capability to staff; done means the affected flows and an agreed design are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
design, frontend, payments
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.