message_update. This behavior makes sens only in message_new when
setting initial parameter of the applicant, not when somebody sends
an email on the record.
Removed priority change when there is a 'priority' key in msg; but
this key is not likely to be present in a parsed email.
Removed updated values change due to a mapping of values present in
the email. This code was a copy-and-paste from crm and did not have
any meaning in hr_recruitment.
Also removed unnecessary code in project, project_issue, crm_helpdesk
and crm_claim for the same reasons as for hr_recruitment.
bzr revid: tde@openerp.com-20131104092731-ixasweoy1dbllbb3
After some experiments, having colors does not seem to give an
usable result on statusbar widget. Indeed we need to have the
current stage highlited, and maybe something to tell that some
stages have a special meaning and/or are the end of the pipe.
The closed field already gives that meaning.
Moreover the issue with the statusbar widget is that it indicates
state and action. Having both dimensions with colors / icons
is quite difficult to understand. We therefore stand on a simpler
version of the widget, only with stages and the current stage
highlighted.
bzr revid: tde@openerp.com-20131021104912-8ybhw0svdoghheh3
- stages: added some fields
-- closed: indicates whether this stage close the working process, for
example task ended, lead lost, applicant hired
-- bar_fold: whether to hide the state in the statusbar; this is different
from fold that is used for kanban views. Viewing a pipe or a specific
record are effectively different things and should use different fields.
-- bar_color: field to customize the stage in the statusbar (still WIP)
- impacted addons: crm, project, project_issue, hr_recruitment
- removed 'closed' addition in project_mrp as this is now in base project
module
bzr revid: tde@openerp.com-20131018132120-h0pv01q2bagtp99x
The delete-rule was initially set to `cascade` in revision
6897.16.13 revid:odo@openerp.com-20120705141706-5gm5mmqode3bvkuc
because the ORM would not allow anything else for the FK of
an _inherits relationship.
This constraint was later lifted in 7.0 server at revision
4681 revid:odo@openerp.com-20121212210247-emrz5rf9ewcwdggu
so we can now switch to the intended default behavior:
when deleting mail aliases we never want to cascade delete
the child records, as that could lead to unwanted deletions.
On the other hand the aliases are automatically deleted when
the record they belong to is deleted, as a kind of internal
dependency. This is the intended safe way to delete them.
There is a special case when the same alias is manually set
on multiple records, in which case you will not be able to
delete any of those records. This is an acceptable exception
and should be manually handled if ever needed, by temporarily
linking the records to delete to new dummy aliases.
bzr revid: odo@openerp.com-20130827150708-62hqk8p7twd527n0
Impacted addons:
- crm_meeting (in base_calendar)
- crm_phonecall
- crm_helpdesk
Removed inheritance towards base_state. Case management (date_open, date_close and duration computation in crm_phonecall) is now directly implemented in write method, to avoid having 2 ways of doing things. Changing state is done through the clickable statusbar widget, allowing to remove most buttons.
Removed base_status module.
Fixed some existing case_* methods in hr_recruitment / project_issue.
bzr revid: tde@openerp.com-20130821132435-skezfvp9phju5tea
Using stages and states is not easy to manage. Indeed those two fields mess with the same basic concept. This task remove the state on hr.applicant model, leaving only stages.
Main features:
- removed base_stage inheritance on hr.applicant model
- removed state field on hr.applicant model
- removed state field on hr.recruitment.stage model
- removed date field on hr.applicant model, not used anywhere; other date fields are considered as sufficient
- added date_last_stage_update on hr.applicant model, holding the date of the last stage change, allowing reporting and analysis on time spend in stages
- date_open is set when assigning an user to the applicant; date_open now means assignation date
This allows to remove nearly all buttons on the form view. As the statusbar is clickable, the only remaining action is to create an employee from the applicant, which is a link button in the form view.
Subtypes have been updated :
- new applicant: stage_id.sequence=1
- other: stage change
Misc:
- [IMP] views accordingly;
- [IMP] reports accordingly, added date_last_stage_update in reports;
- [IMP] subtypes: New, Stage Changed and Hired are kept;
- [REM] removed some tests because they are not applicable anymore;
- [DOC] doc directory + changelog + stage explanation;
- [REM] removed hired.employee wizard
bzr revid: tde@openerp.com-20130709115904-o9ac29fesu3lreol