dvorka/shifts-solver

Finds a solution to fitting employees with preferences in a schedule for shifts-based operation (GWT, Google AppEngine).

shifts-solver's Issues

Solution editor: flex table w/ radio employees, color codes and explanation

Improve change employee dialog by putting there a table of employees w/ color code (red is employee who should not be allocated) w/ explanation (role, busy, jobs, ...). Employees (table rows) will be radio so one of them will have to be allocated anyway.

Solution panel: all tables localization

Solution view panel to become solution EDITOR

Allow solution modifications w/ integrity checks - jobs, filled shifts on day, ... This is a way how solution could be tweaked in any way. Solver is just a hint and in principle solution editor could be enough - instead on paper, she would do it in editor ;)

In other words this might be the most important feature - perhaps editor will an only way how to create a schedule (a lot of rule violations) and editor might be more useful than an Excel.

Imagine view where left most column is date and shift type. Other columns within table contain names that MAY serve - have role, continuity, have capacity for jobs and nights, etc. Below table is employee allocation statistics showing load, jobs, balanced night and day shifts, etc.

Per every workday employee has holidays add 1 job

• MD rules

Add organization's mail among authorized users

Tx period preferences persistence: orphan day prefs sometimes remain

SHOULD rule: editor to serve on Sunday night + settings checkbox

Black table headers review

Incorporate positive preferences use (sorting)

Rozpisy table (list) not refreshed on creation of a new rozpis (should be done on left menu click)

Preferences name to contain timestamp: (2015/11/30 10:21)

Custom total shifts/month (preferences edit - per employee in month)

Day preferences persistence broken (disapearing)

My code is fine - just eventual consistency? Holidays and other preferences are disappearing on saves. Can it be too early kill on eventual consistent?

Localization of preferences table

Last month editor not set on load in pref load panel

Solver on genetic algorithms

GA is an approach to searching a minimum of a function. Create a function that valuates solution (state) and gives 0 to valid solution, while any partial solutions get valuation > 0.

http://de.mathworks.com/help/gads/how-the-genetic-algorithm-works.html
https://github.com/lagodiuk/genetic-algorithm

Data backup via REST

MUST rule: Saturday & Sunday > no Monday + settings checkbox

If employee serves on Saturday and Sunday then it CANNOT serve on Monday.

Employees - sportak column - sportak not rendered yes/no

Dayweek doesn't work at preferences

Day in week Sun - Sat is wrong for months.

Partial solver

Remember what cannot be solved, don't fail but move forward.

Public holidays: add Velikonoce for next 5 years (function will get year as parameter)

Period solution GAE persistence

Jobs @ rozpis not updated on solution edit

5 sluzeb + 1 den volna

On failure print (Solver) Failure Explanation panel

The purpose of this panel will be provide enough information to determine why solver failed while looking for a solution:

• clone() employee allocations
• store them along with max* fail
• render them in new panel + flextable w/ explanation and hints

Email employee attribute

Email to be used for authentication and authorization (employee view) while admins will be hardcoded.

Custom shifts for month

This is MUST feature (to be added to MD as well). Preferences panel, Employee column to be split - below name will be "Jobs: 12" with editable number + jobs will have to be solved to preferences (persistence).

Employees table @ Solutions panel NOT hidden! on load from solutions table

Morning and afternoon shifts to be balanced 50%/50%

Do it via sorting:

• Employees with the same other parameters will be sorted by this ratio as the last criterion.
• Make this sorting an option in settings (may cause solution not to be found)
• Add a column showing ratio to employees overview table.

Total shifts/month: even month round down & odd month round up

• MD rules

Solution editor: split employees to valid and invalid (and why) to help w/ decision

... or add comment to drop down why they should NOT be choose (OK employees in drop down has no comment).

New employee/prefs > not stored to RIA state > not visible in table

Employee allocation: on holidays user gets shift - seems to be incosistent

... some employees get day, other don't in employee allocation constructor. Find out why...

Solver & last month connection: must change in UI (not save) to make it work :/

... I see - what's in RIA state matters ;) i.e. there is a problem in loading last month employee in textbox

UI for employees to specify prefs

• different bean
• employee prefs will be built on demand from these other beans - controlled influence

En locale contains "ano"

Drone > Staffer / Redaktor

No solutions > solve() > save() - left menu not updated

Left menu not refreshed on new and/or deleted employee/prefs

Missing second workday 8am drone!

Show M+A for editor continuation (2 shifts in one day) in solution

Period preferences - on month change PPs are duplicated & not loaded, key issue?

Application view for employee to enter their preferences

• secure admin areap
• add a random key corresponding to a user (will be in flex table) - this will be used in a ling to access a page where to specify preference http://...?e=h83ad&y=2015&m=11 while year and month will be validated. Preference to be stored to a separate bean.
• user will not have to have Google account - these page will NOT be secured and only key will be used.

Employees table: hide email column (for now)

Jobs/allocations calculation: editor to get -1 for FRI to SUN

Don't add shift to editor on Sunday afternoon (comment in source code for explanation).

Capacity calculation: not enough (sportak) for the month

Determine amount of shifts needed for the month and compare it with employees (with holiday preferences) - is there even big enough capacity prior starting to solve?

Validation solution: everything is red