Columns for leaderboard:

Sort by number of x's y'd.

If there is a pending file highlight the row in yellow, only show approved if there are NO PENDING files

Drop phone number

it seems we need it

use term and id as the body content

create a new waiting room for a cohort of people who said yes to a competition and were forward from phoenix

This should have node id, run id, and signup dates

DoSomething/legacy-website/issues/6170

Transformers, robots in disguise!

Implement the use of API response Transformers using Fractal and add an API key so POST can't be sent to Gladiator anonymously!

Relates to recent work completed in #44

As an admin I want these variables to be replaced in emails

• campaign title
• campaign_link#prove
• repoortback_noun
• reportback_verb

instead of showing contests on the main contestants view
paginated that view

New DB structure.

Overview: A Contest is the umbrella container for everything. Each Contest has one Waiting Room that has sign up dates tied to it that can be set and edited by an admin as needed. Waiting Rooms get split into Competitions. Competitions hold groups of users competing in a contest and store the date the competition starts and the date they will end based on the run period of the Contest.

Contests

• contest_id
• campaign_id
• campaign_run_id
• waiting_room_id
• How long the contest runs for (duration)

Also has (currently undetermined) metadata such as:

• title
• description
• prize (?)
• rules

Waiting Rooms

• waiting_room_id
• contest_id
• signup_start_date (admin can edit)
• signup_end_date (admin can edit)

Waiting Room Users

NOTE: I think this table exists already and should still work with this new structure:
waiting_room_id
user_id

Competitions

• competition_id
• contest_id
• competition_start_date (based on the day this competition was created)
• competition_end_date (calculated based on run_period and set on creation

Competition Users

• competition_id
• user_id

via NS

on contests
and compeitions

some of this functionality is in aurora

this should no longer be metadata attached to the contest, the duration or end dates should be set when you make the competition

As an admin I want to select the end date after I split the waiting room

• easy way to pull users
• or a queue to send messages

users in a competition should be displayed with their reportback activity

Update the waiting room CRUD methods and views to work with the new DB structure.

After #56, we are now creating a waiting room automatically when a contest is created. We still need the option for admins to be able to view all waiting rooms, edit waiting rooms, etc.

I'm not sure we need to expose the create form anymore but open to thoughts on that.

store user info in cache

• first name
• last name
• email
• mobile

this part may be vNext

• signup and rb data

Need to be able to grab all users, or pass an array of Northstar user IDs and grab the info for those users.

Forgot to add this in #48

coming from @mikefantini

• set the waiting room to be open for X time, a month let's say
• you can view how many people are in the waiting room on the contest view

Update the waiting room split functionality to work with the new DB structure, not sure how much of this needs to change, but this is a general outline of what should happen.

• There is one waiting room per contest.
• When the sign up period is over there is an option to split the room.
• The room gets split in to competitions.
• After split, the users get removed from that room and it can be reused if needed.

from staging

store that info in cache

deployyy

This endpoint can replace #26

Phoenix should be able to hit this endpoint to see if there is a contest on a node and the response should include if the signup period on that contest is open (based on the dates on the waiting room).

Create the following migrations:

• users
• roles
• role_user
• waiting_room [id | nid | run_nid | signup_dates]
• competitions [id | nid | run_nid | comp_dates]
• competition_user

it would be a lot easier to create a waiting room at the same time as a contest, so let's add the waiting room start and end dates to the contest form

Login authentication via Northstar needs to return list o' errors and show them to the user when logging in.

"Retrieving many" from the cache seems to vary how the results that are not found come back... as either false OR null which is confusing and seems like there's an underlying issue to look at.

• tables should be sortable by various things
• expose rb quantity
• updated_at

refs #18

automatically running and tested before merging

http://fractal.thephpleague.com/ 🎉

Refs #22
Refs #26

since we are holding off with messaging, need a way to get user info to mail merge send reminders and leaderboard updates
refs #23

phoenix needs to ping this app to determine if there should be a competition on the node.

See discussion here: #37 (diff)

the amazing table @sbsmith86 added in this PR #30 should get implemented on the /competitions page as well I think ( @angaither ?)

Falls in same boat with methods related to #22

you can access /contests/create without being logged in

refs #77

• add waiting room end date to the table index
• create two tables of contest index
  • open contests show on the top
  • closed contests show under in a different table

because we <3 patterns 🎨

After the signup dates in a waiting room has ended an admin needs to be able to split users out into competitions

When a user confirms that they would like to sign up for a competition, Phoenix sends a post request, and need to implement an endpoint on Gladiator to receive this post and add the new user to the User tables and place in appropriate waiting room.

Update the competition CRUD methods and views to work with the new DB structure as needed.

• Should be able to view competitions based on the contest they are apart of. Add the ability to sort by Contest, and the ability to filter for a specific contest.
• Sort competitions by start and end dates.

It'd be helpful to know how many users are in a waiting room (and ideally who they are) before deciding to split or not.

Ideally this could be a new column on https://qa-gladiator.dosomething.org/waitingrooms where the number of users displays in the table and links to a view of who those users are.

Number of people in the waiting room should be the priority. This way Hillary and Chris can know how much traction the competition has received and if they should split it sooner rather than later given demand.

I would like to take a stab at starting to write some tests for this app. Starting with some basic controller tests

• Hide contest id on edit of waiting room, this isn't super useful, especially if it's inherited on the contest form
• remove routes to create/edit waiting rooms explicity
• remove the waiting room link from the nav

• remove all competitions link from the nav
• pull the filtered competitions table into the contest view
• be able to access the list of users in the waiting room
  • show total number of users in waiting room
• show list of competitions

Now that we have the concept of Contests, we need to create CRUD methods for them.

• First Name
• Last Name
• Email
• Cell
• Reportback admin link
• Flagged Status
• Quantity
• Northstar User ID