codebar / codebar/planner

Ability for admin to subscribe any member of a chapter to a workshop

Open
#627 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Ruby
Stars
104
Forks
205
Avg merge
1d 5h
Merged PRs (30d)
63

Description

Description of the issue 📄

On the admin workshop view (admin/workshops/:id) admins have access to a dropdown that allows them to manually subscribe members of a chapter to any given workshop. Currently this dropdown is populated with members who have received but not accepted an invitation email. This is causing issues for the London chapter as we have stopped sending email invites for that chapter. Update this dropdown to show all members of a chapter who have not yet RSVP'd to the workshop.

Screenshots 📷

screen shot 2017-11-24 at 21 11 50 Dropdown to update

Steps to fix 🛠

Update the behaviour of the dropdown in the app/views/admin/workshops/_invitation_management.html.haml partial.

To do 📋

  • Claim this issue (comment below, or assign yourself if you are part of the codebar org)
  • Fork and clone the repository
  • Update the relevant files. Follow the steps to fix section in this issue.
  • Commit your changes as one commit. Use the title of this issue as your commit message
  • Submit a pull request, make sure you mention #codebar24PR2017 in the description
  • Mention this issue in the PR description by including it's number
  • Have your pull request reviewed & merged by a codebar team member

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 in app/views/admin/workshops/_invitation_management.html.haml and inspect how the dropdown currently filters chapter members. Trace the existing invitation and RSVP data used there, then verify that members who have not RSVP'd appear regardless of invitation-email status. Done means the admin can select any non-RSVP'd chapter member for the workshop.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
full-stack
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.