rubyforgood / rubyforgood/casa

reimbursement requests

Open
#7,041 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

✨ New Feature Help Wanted no-issue-activity
Dominant language
Ruby
Stars
381
Forks
542
Avg merge
3d 15h
Merged PRs (30d)
47

Description


Sarah Bosken  | Sarah Bosken  | Fri, May 1, 11:03 AM |   |   -- | -- | -- | -- | -- Sarah Bosken  to me | to me to me

I know that the reimbursement requests go into our queue and then when our coordinator completes them she marks them as “done” to get them off the queue.

 

Is there a way when that box “reimbursement done” is checked, that the volunteers could get an email notification so that they know to keep an eye out for the reimbursement check in the mail? And, in the alternative, is there a way for them to see that the reimbursements haven’t been completed (we do ours once a month) so that they aren’t emailing their Supervisor to ask if their reimbursement has been completed yet?

How to access the QA site
Login Details:
Link to QA site

Login Emails:

volunteer1@example.com view site as a volunteer
supervisor1@example.com view site as a supervisor
casa_admin1@example.com view site as an admin
all_casa_admin1@example.com view site as an all casa admin
go to /all_casa_admins/sign_in
password for all users: 12345678

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reimbursement workflow on the QA site, using the volunteer and supervisor views, and trace where the “reimbursement done” state is recorded. Clarify whether the intended result is an email notification, volunteer-visible status, or both; done should make the chosen completion state reliably visible to volunteers without follow-up emails.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.