One employee may be hired and fired several times during the history of our company. (For example she may go to a parental leave and return to the work later.)
The table has the following fields:
- employeeid (the ID of the employee)
- hired (date)
- fired (date)
- firereason enum('fired','left','parental','vacation','sick','death')
- comment text
As you see there are a number of fire reasons:
- 'fired' (forced to be fired by the boss)
- 'left' (left the job by his own will)
- 'parental' (left for a parental vacation)
- 'vacation' (non paid vacation)
- 'sick' (sick leave)
- 'death' (death)
I want to present the list of pairs of hire/fire to the editor as a table, sorted by hire date.
Note that for the last hire/fire record fire date may be missing (null), if the employee for hired but not yet fired.
I am lost about more details how it should be presented and interacted.
After some additional thought I decided that it is best to present the information as a static (non-editable) table with "Edit" buttons in every row.
Now an additional question is arisen: Should "Edit" open a modal window above gray background or an additional row in the table? Which of these two variants is better? Also which buttons should be present in this additional row: "OK", "Cancel"? Can we switch to editing an other row without pressing "OK" or "Cancel"?