Where should facilitators see the emails AWBW has sent them?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- full-stack
Research direction
This is a product decision, not a code change yet. Read PR #2671 to see the new simple "Edit my profile" page, then find the full person edit form's list of portal emails sent to the owner. Wait for stakeholders to pick one of the three options in the issue. Done means that choice is recorded in the issue and the email list is reachable as agreed.
Written by the indexing model from the issue text.
Description
🤖 From Claude:
Question for stakeholders: should facilitators be able to see a list of the emails the portal has sent them? If so, where should it live?
Background
- The full person edit form shows the owner a list of portal emails sent to them: confirmations, reminders and bulk sends. Hand-logged staff communications stay hidden.
- PR #2671 sends facilitators to a new simple "Edit my profile" page instead of the full form. Nothing links them to the full form anymore, so they can only reach that email list by typing the URL.
Options
- Add an owner-only "Emails we've sent you" section to their profile page.
- Add it to the simple edit page.
- Drop it for owners; staff can still see it.
- Dominant language
- Ruby
- Stars
- 15
- Forks
- 28
- Avg merge
- 14h 29m
- Merged PRs (30d)
- 292
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from rubyforgood/awbw
-
blocked
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
rubyforgood/awbw#2824 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rubyforgood/awbw#2822 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rubyforgood/awbw#2160 ·
Maintainers usually reply within 1 day
-
Update callout faq defualt text when the new person subscription launchesPossibly taken @maebeale claimed this 98 days ago. Openblocked
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rubyforgood/awbw#2095 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
rubyforgood/awbw#2088 ·
Maintainers usually reply within 1 day
All issues in rubyforgood/awbw
Similar issues
-
Bug Ruby
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
getsentry/sentry-ruby#3211 · 1 comment ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
internetee/registry#2984 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ecosyste-ms/issues#862 ·
Maintainers usually reply within 1 day
-
Redis Lua error `@user_script:52: ERR value is not an integer or out of range` when `window_size` is configuredPossibly taken @mimosa claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
riscv/riscv-unified-db#2829 ·
Maintainers usually reply within 1 day