propedeutica / shift-reservation Goto Github PK

The list of grades that can be used to create a new offspring should be limited by configuration.
Although the model is ok, the controller should check that there is no error or send a flash message explaining the situation.

A full web page could be used describing steps to follow when the offspring is not in the grades configured

• After updating a shift's information the the user is redirected to the Room_Index view. It should redirect to the view showing the changes of the given shift.
• This is how the system redirects the user at the moment. Will work on this issue myself.

To avoid problems, all surnames of the offspring of the same user should have the same surname.
That doesn't cover some edge cases, but it a good measure to avoid problems when "good neighbors" want to help

When creating a Graded Offspring: Grade attribute sould be configurable.

Sometimes user create more than one account with different emails.

As an administrator, I want to be able to find those duplicates and act upon them

• In the Add shift view there is no option for the user to Go Back to the Room_Index using a button. Only using the main menu-bar. There should be a button in this view.
• Also 'add shift' button is not capitalized

The administrator should be able to resolve most of the common problems for a new user:

• They didn't sign up properly
• They didn't receive the confirmation email
• They couldn't create offspring
• They didn't assign offsrping properly

• When Updating a Room's information, current view only gives the user options to 'Delete Room' and 'Edit Room' and it should have a 'Cancel' button to go back to the Room Index.

• When Updating a Shift's information, current view only gives the user options to 'Delete Shift' and 'Update Shift' and it should have a 'Cancel' button to go back to the Show Shift View.
• This is how the view looks at the moment. I will work on this issue myself.

• When adding a new room, the system allows to use very high values (not realistic) in the "Capacity" attribute.
• There should be a validation before accepting the addition to prevent the user to enter a value higher than the Maximum capacity that the admin can configure.

Allow the admin to choose between:

• Customers choosing shifts themselves (no offspring)
• Offspring being assigned to shifts (no parents)
• Both

And configuring it in the environment, the configuration does not need to be dynamic, but has to be documented

• A controller for offspring must be created with its corresponding specs.

Bootstrap switch is rendered as a a checkbox instead of a switch

See rspec for more details

• Users
• Rooms
• Shifts
• Assignments
• Offsprings
• Confirmations

• When adding a new shift the system should not allow the user to create a shift starting and ending at the same time.

           Example:
                    Start time: 14:00
                    End time:   14:00
  

• This should be invalid

there is a global lock to avoid changes in the system.
When the lock is on, a user should not be allowed to:

• Create or update assignments
• Create or update offspring
• Create or update users

When showing a Room's information, current view only gives the user options to 'Edit' and it should have a 'Go Back' button to go back to the Room Index.

Such button should flash a message to the user indicating the redirection.

Deleting rooms is a process that need a confirmation button. The deleting process is very fast and the button "Delete room" can be clicked by mistake.

Export lists as csv:

• Users
• Rooms
• Offsprings
• Assignments
• Shifts

Currently, the user has to write down the time in an specific format hh:mm.
IT should be more visual, and easy to use

Assignment need to be

• unique
• identified by creation and modification date
• a user should not be able to modify the assignment of another user
• administrators should be able to modify every assignment

Users should receive:

• Confirmation email
• Devise emails: (reset password, etc)
• Welcome email
• Offspring assigned email
• New assignment email
• Close account email

When showing a Shift's information, current view only gives the user options to 'Edit' and it should have a 'Go Back' button to go back to the Room Index.

This is how the view looks at the moment. I will work on this issue myself.

If you leave the user long enough, it will time out.
There are two messages when that happens:
You have been logged out
true

The second one makes no sense

Current view of add shift doesn't indicate to the user the time format that needs to be followed in order to create a valid shift (hh:mm). If a simple hint or help line is added, a lot of users wont need the error messages to write the start/end times properly.

Configure the system to be compatible with configuration for OpenShift Online

Alllowing the user to choose between 5 days week or 7 days week, with a change in configuration. It should not be dynamic, just an option in configuration

Create user model

• When adding a new shift several error messages are displayed to the user at once when the format is incorrect. Should be less messages and better explained.

Convert about into a modal instead of a route, following patternfly guidelines