(formerly #8526) Update Make Payments screen in Gov 2.0 Site for Online Banking
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
### ServiceNow incident: n/a
### Contact information
Staff Name: JH
### Description
Can we update the modernization page for clients to have more details about how Online banking payments work. Perhaps more detail about it’s limitations…….can’t use for future effective filings, and delay in receiving outputs until payment is received by our office. At the moment all I see on the page is this info:

### Ops Process
- [ ] Add **entity** or **relationships** label to zenhub ticket
- [ ] Add 'Priority1' label to zenhub ticket, if:
- If the business says it is a priority
- BA can use their business knowledge and best judgement if it is a priority or not
- How long the ticket has been open
- If we are still unsure, reach out to other BAs in the guild
- [ ] Assign zenhub ticket to the current developer on ops rotation
- [ ] When ticket has been created, post the ticket in RocketChat '#Operations Tasks' channel
- [ ] Reply All to IT Ops email (CC BA Inbox) and provide zenhub ticket number opened
- [ ] Dev/BAs to resolve issue
- [ ] **DEV**: Enter the time you worked on the ticket in the estimate
- [ ] **DEV**: Tell BA it is ready to review
- [ ] BAs review
- [ ] Add ticket to the current milestone of the code base the ops ticket was relating to (i.e., if it's a Name Request issue, assign to current entities milestone, etc.)
- [ ] Close Zenhub ticket
- [ ] Tell IT Ops to close the ServiceNow Incident
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue points to the Gov 2.0 site's Online Banking payments modernization page but names no file. Start by locating that page in the frontend; it is done when the page explains the limitations on future-effective filings and the delay until the office receives payment.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100