hr_simplify - job_id not being stored in the database on contract creation

[Salton Massally]

Hello, on creating a new contract for an employee, even though the new contract_id is stored against the employee's record, the new job_id is not. The job_id is only stored when that contract is edited and the job changed. This makes things like sort and search that depends on the job_id actually being in the table to not work.

I raised the priority of the job_id store priority as I reckoned that the trigger for checking if any of the fields being watched changes, e.g contract_id are being run before the one that records a change in the contract....

I'm not very good ay explain but I guess you understand my point.

Thanks