Some issues we noted before the usability study and that we want to fix after Summit:

• Spot CRUD screen: column "skill set" should be renamed to "Required skill set"
• Button "solve" lingers
• Publishing a part that has unassigned shifts should give a warning about that first.
  • In any case, we need a dialog before that goes through anyway.
• smaller screen size when solving leads to weird layout
• Adding a shift has 2 forms in which "nothing happens, despite the click"
  • Clicking in the spot header row. This should spawn a new shift too.
  • Dragging for 1 pixel instead of a pure perfect single click. Matthew and Geoffrey ran into this very quickly. this too should spawn a new shift. We could even say it spawns a new shift and immediately starts deciding the lenght of it (like in google calendar). Minimum lenght is 30 minutes for example.
• Do not scroll down in spot roster view, so at the top of the screen, edit a shift. notice that the grayed out area has this wierd extra gray bar in the datetime header.
• In a spot roster with 11 spots and 10 spots, go to the last page with that 1 spot and try to edit one of the shifts if there is only 1 or 2 lines. That's impossible.

Others I see:

• Solve button left of publish button, as that happens first