The orgman from valleyjo

Currently a flash message takes up the entire width and looks kind of weird. Maybe putting it in a 12u container would give it some space on the sides

Add more fields for registration

Leaderboard with no required event types does not display "Other" table column header

The leaderboard does not display the "Other" point category when there are no required event types in the database, It displays nothing where "Other" should be.

Having at least one required event type solves this problem. This is a low priority bug because this situation is unlikely.

Backlog

Comment on this issue with feature ideas

Log in system

Dismiss page alerts via JS

User profile picture uploads

I can help you with this one. We should be able to easily move our code from the old app to this one

Tasks

(From developer's viewpoint, what are the tasks? For example tasks may include user interface, database manager, data mining, profile management, and so on. Cost analysis is based on tasks.)

Add tests for excuse model

Fix styling on the callouts

Update user positions

Admins need the ability to update user's positions

Fix hard coded API key in LinksController

Attendance

Create Event types
Create events
Users edit events if they have a position and an event belongs to their position
Points Leaderboard
Users can submit excuses and get approved

Add tests for fine model

Styles broken in production

For some reason the bootstrap gem doesn't appear to be working in production although it works fine in development and test.

Add verified users to DB seed

Missing Tests

Structure model tests similar to event_types_spec.rb. Be sure to test each state possible for a valid and invalid model.

Leaderboard

names are sorted by highest overall attendance
only required event types are listed as columns
The other column has the total of all non-required event types

Event Types

model validations already exist

Only the secretary can visit event_types_path
Ensure web based CRUD works

Events

Expand on model validation tests
Event listing page displays all events
As an event type administrator, any event that is your type should have a link to it's respective edit page
If you're the secretary you should have links to the edit page for all event types
User should be able to self report their attendance if it's enabled
User should not be able to self report attendance if not enabled
User should see message notifying them that they can't self submit attendance on events without self submit enabled
Users that aren't event type admins can't edit, create or update events

Quick Links

Expand model validations
Any user can add a link
Only the user that added a link can see the remove button
The secretary can see a remove button for every link, even if he/she didn't add it
Secretary can see a remove button for all links
Links with an expiry date in the past should not be displayed
Links with an expiry date in the future should be displayed
Links saved with no expiry dates should display expiry time as "never"

Pending Approvals

A pending user cannot log in
Pending approval page lists all pending users
Pending approval details section should say "none provided" for missing info
Approve as active approves the user and sets their status to "Active"
Approve as inactive approves the user and sets their status to "Inactive"
Reject user deletes the user from the DB and sends them an email that contains the rejection message

Update Users

Position model validations (must have user_id, must have either name or event_type_id but not both. Look at event_types for how to validate mutual exclusivity. Additional validations need to be added to the position model to support this scenario.)
To Inactive box displays both active and alumni members
To Alumni box displays both active and inactive members
To Active box displays both inactive and alumni members
Update user positions section does not show positions event types as a position
Update event type admin only shows all available event types
Not yet built
Update Users and Update Event Type Admins can be set and unset

Fines

Model validations
Fines should be assigned when an event took place in the past and it has a fine associated with it and the user did not submit an excuse and the user was not present (see Attendance::FinesController#update_fines)
Fines that are assigned to a user should be displayed on fines_path
Outstanding Fines page marks fines as paid when clicking the "mark as paid" button

Combine admin/users_controller and update_users_controller

Refactor event_type delete route as destroy

Add ability to set positions for event types

As an admin
I want to give users' positions that correlate to event types
So that these users can add new event types themselves

Finish Event Type Delete

When you delete an event type all events of that type should be moved to miscellaneous event type.

Deployment

Figure out a deployment strategy.

Test user PR

Verify that users are actually saved to the database

Submit excuses for required events

Bootstrap integration w/ our templates

Role call input for attendance

As an event type creator
I want to click individually through member's names
So that I can do an easy verbal role call

Questions for Bill

How do you make a scope with multiple conditionals that are not equality
Should we make our statuses constants on the user model? (yes)
UI for org chart admin
Roll call advice
minimum acceptance criteria

As an admin
I want to be able to mark fines as paid
So that the fine database stays up to date

before_create for event.semester
event excused field should be event.attendance.accepted
before_create for link.expiration
set excuse.accepted to false by default
set fine.paid to false by default

Differentiate between pending and rejected excuses on the excuse display page

Sales Presentation

Sales presentation – 3 minutes
Software plan – 3 minutes

Deliver a hard copy of software plan after presentation

Update user status

Admins need a way to mark users as active, alumni or inactive.

Resources

Resources needed to complete this project.

1. Hardware (for development and for deployment)
2. Software (what do you need for the development environment?)
3. People (introduction of personnel and their roles)

Scope

Product overview and summary.
Evolves into Sec. 1 of requirements spec

1.1 Functions (What can this product do? Evolves into Sec. 3 of requirements spec
1.2 Performance (How well can this product do? Evolves into Sec. 4 of requirements spec.)
1.3 Limitations (What this product cannot do? Included in Sec. 8 of requirements spec.)
three or four pages double spaced
include change history

valleyjo / orgman Goto Github PK

orgman's People

Contributors

Watchers

orgman's Issues