Add an extra option to allow people to explicitly say that they are not attending a meal.

In the menu details view allow the possibility for the user to tell if he/she will be attending lunch

For dishes / menus / schedules, add a confirmation dialog when the user attempts to delete something.

Google sign in was implemented, but new users still have to be added to the DB so that they can say when they are attending lunch

Every week (Monday, for example) a friendly reminder should be sent to all users, to remind them that they should update their attendance.

A dish has detailed information about the food that will be available and it will be associated with one or more menus
No FE is necessary at this point.

A Menu is a simple entity with an id and a name that will be referenced by a Dish.
No FE is necessary at this point.

This entity will held mapping between menus and the days they will be available

The days available to the admin will be all days in the calendar.
We may want to book other lunches or meals for other days

Description

The user should be able to select for a given date only one scheduled meal if there are planning to go to any of the available locations.
For that goal a new column should be added, Location, which shows where it's scheduled.
Also, for UI consistency sake the user should still see a checkbox for the selection, but with the caveat that would only be possible to select only one location per date (this validation should happen on the frontend as well as in the backend).

On why use a checkbox and not a radio button: Certainly a radio button would make things easier on selection, validation wise, since you would be allowed to select only one option. But this has two drawbacks:

• When there is planed meal for only one location (this is going to be unlikely in the future) a radio button doesn't make sense.
• On the scenario where you want to erase your selection, for example when you're on holidays but mistakenly selected a date. For which we need other solutions.

Users

Everyone

Depends

On #99

After the user is logged in in the application,
a list of days with date and menu name should be presented to him/ her

Create endpoint to:

• add new menu per certain day
• list all menus for all days available
• delete a menu for a certain day
• query menus per day by UUID / menu UUID / date

Add flash messages to the top of the screen after the admin has created a new dish, menu, or schedule

Create endpoints to:

• add new menu dish
• list all menu dishes
• remove menu dish
• query menu dish by UUID / Menu UUID

I have noticed that when editing a menu, clicking in the labels of the dishes to select them, selects always the first dish.

To solve this issue check the code for the code for newMenu.scala.html, line 22. An index has to be added!

Check as well if this issue is happening in any other view

Create endpoints to:

• add menu
• list all menus
• delete menu
• query menu by UUID / name

update from1.1.1-P25-B3-SNAPSHOT to 1.1.1-P25-B3

Add a minimum amount of keyboard shortcuts.
Pay attention to do not override any import browser / system shortcut.

Create endpoints to

• add dish
• query all dishes
• query dishes by name / UUID
• query all flags in dishes (IsVegetarian, IsGlutenFree, ..)
• delete a dish

The MailerUtils is dead code, not being used. Please remove it

By default, show only future meals in the "schedules" separator.

Add a date range filter that allows filtering a custom time frame.

(Depends on issue 99)

After adding locations to the lunch planner, modifications in the UI have to be put in place.
One option would be to add a location office to the profile of the user, but the truth is that we want people to be able to easily choose if they are going to Rotterdam or Amsterdam office on different Fridays, so this may not be the best option.

In summary, after adding locations to the app, make it work nice in the UI 😄

Description

The user should be able to define where a 'scheduled meal' is going to happen.
When creating an new 'scheduled meal' the user should see a dropdown with just two options:

• Amsterdam
• Rotterdam

The selection must be mandatory.

Users

• Admin

=================================================================

Lunatech is growing and lunch has to be organised for more than one office on Fridays.
The current version does not have the notion off a location for the planned meals.

For admin users, add the possibility to add / modify locations.

The option to delete can also be added, but at least add a confirmation dialog to it.

@dirkjonker gave the idea of synchronising the lunch and vacation apps!
We don't want the user to lose any previous choices, so i think this features has to be user-proactive.

A simple button that allows the user synchronise both apps. If the user is on vacation a certain Friday, then the attendance should be set automatically to "Not attenting". Simple! Simple!

TODO: check with the vacation app people if this can be done

This entity will held mapping between dishes and the menu(s) it belongs to

Show only future meals in the "planned meals" separator

From the list of days/ menus the user will be able click on the item in order to see it's details:

• menu name
• dishes in the menu (with dishes details)

Add the scalastyle and scoverage plugins to generate reports to make sure the code quality of the project.

The current google api credentials, in order to use the Google Authorisation are linked to my lunatech email account!

Contact Sietse/ Erik Bakker in order to find out to who can create these credentials in a lunatech "general" account and modify it on the clever cloud env variables.

It would be nice to have an option to have some lunch option selected by default.
For example the option for which there were the most votes.
And only not to get lunch if you select option ‘no lunch’.

Add a user profile separator that allows the user to add information about diet restrictions:

• is vegetarian
• does not eat sea food
• does not eat pork
• does not eat beef
• does not eat chicken
• does not eat gluten
• does not eat lactose

Add the possibility of selecting all or unselecting all meals in the "planned meal" separator

When a separator in the side bar is selected, there is no visual evidence of it.

The administrator has added more than one menu for the same day hoping that people would choose only one of those menus (for the same day), but the app allows the user to choose for more than one menu in the same day.
Add a validation that does not allow this and explains the user that is case of more than one menu in the same day only one can be selected

Create endpoint to:

• add new menu per certain day for person
• list all menus for all days and persons available
• delete a menu for a certain day for person
• query menus per day per person by UUID / menu per day UUID / user UUID

depends on:
user profile implementation

new functionality
Add to the list of people attending a meal a summary of the diet restrictions

Create the entity user, model and DB
Search for users by UUID and email address should be available

Now that the lunch app supports meals at different locations, this need to be reflected in the monthly reports.
The organization of the information is an open point. You can ask Shelley what is her preference

In the list of days / menu add the possibility for the user to tell if he/she will be attending lunch
The user should not need to have to enter the menu details to say if he/she will attend lunch

In the admin beside the number of attendees to a certain meal, in the details of the schedule, add the list of people that is attending the meal.

I would really appreciate a monthly report with the total amount of people who have had lunch. This is for tax purposes.

This entity will held mapping between people and the days they will attend the meal

This is related to #95, #75.

The idea is to create a Slack bot to remind users (via direct message) and ask them is they'll be attending the lunch or not. This will give the convenience for users to decide via Slack and by not going to the lunch app. This will also give better tracking and better data for the monthly report.

Lunch bot specs:

1. Will remind all user (who have not responded yet) to make a decision whether they'll attend or not
2. Reminder will be every Tuesdays and Thursday (10 AM)
3. Choices are: "YES, I'll attend" and "NO, I will not attend"
4. Will state that user can still change decision by going to lunch web-app
5. Bot will state the menu and location
6. If there are more than 2 locations for one day, the choices will be: "YES to Amsterdam", "YES to Rotterdam" and "NO, I will not attend"

Feel free to add, edit the bot specs.

When the Lunch app was created it was not known that reports about who attended a meal were necessary. Because of this whenever data is deleted, a hard delete takes places.

Issue: Reports of past months have little data, it's known that more people have attended the meals. Data has disappeared.

Resolution: Let's created a "Deleted" column in the BD that will just mark the data as deleted.

Currently when, for example, a dish is deleted, all related data is deleted as well because of foreign keys in the BD