rubyforgood / rubyforgood/human-essentials
Investigate whether we can get information from sendgrid about failures and give that to the banks.
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 593
- Forks
- 593
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 41
Description
Summary
We want to shorten the bad email, get that info to the banks, get it fixed cycle, and possibly get Scott out of the middle of it.
Details
Scott will do initial investigation
What might we want a user experience for this to look like.
As a line in the dashboard that only shows up if there are problems -- make it at least yellow.
Give them the list of emails that failed
So we might be able to do something with this without an actual table in our system using Sendgrid APIs. Scott will do a bit of poking and get back to us.
We will update this issue with findings to go forward.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating whether SendGrid APIs expose the failure details described in the issue. Review the proposed dashboard experience and determine what information should be shown to banks. Done means documenting the findings and a decided path forward, since the issue currently contains no named files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100