hackforla / hackforla/tdm-calculator

Product: Get stakeholder feedback on where to direct users to report system failures

Open
#3,441 1 comment 0 reactions 0 assignees View on GitHub
deck: stakeholder presentation feature: Stakeholder options level: easy priority: MUST HAVE role: Product Management size: 0.25pt
Dominant language
JavaScript
Stars
68
Forks
47
Avg merge
3d 9h
Merged PRs (30d)
25

Description

### Overview
We need to ask the stakeholders where they want users to report systems failures (email address) and language so that it is consistent across the application

#### Details
Example of a system failure - SMTP / TDM Google mailer failure

- Error message
Sending the verification email to your updated email address failed. Please contact technical support.

Image

### Action Items
- [x] Add to staging
- [x] Review slide with product
- [x] Get Stakeholder input via the stakeholder meeting slide deck
- [ ] Make a new issue to revise the wording on Account Update failure notice
- [ ] Discuss with dev other places the notification would be appropriate

### Resources/Instructions
-

#### Staging and Release decks
- [Staging Deck](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/)
- ~[Slide 304, #3441](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/edit?slide=id.g3f74bf8e22b_33_17#slide=id.g3f74bf8e22b_33_17)~
- Release Deck
- [2026-08-18 Release deck, slide 3441](https://docs.google.com/presentation/d/16-zgcjRJ6zjrAeTPZatTKdOAhuyhhqiN6bPsCsp0Huc/edit?slide=id.g3f9ae231ea1_0_195#slide=id.g3f9ae231ea1_0_195)

Contributor guide

Open the contributing guide

Research direction

Start with the linked Staging and Release decks and review the completed stakeholder-feedback action items. Confirm the preferred support email address and wording for system failures, then document the decision and create the follow-up issue for the Account Update failure notice and other appropriate notifications.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.