[MERGE] [REF] project task/issue stage management cleaning

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 project.task and project.issue models, leaving only stages.

Main features:
- removed base_stage inheritance on project.task and project.issue models
- removed state field on project.task and project.issue models
- removed state field on project.task.type model
- added date_last_stage_update on project.task and project.issue models, 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 task / isuse; date_open now means assignation date

This allows to remove all buttons on the form view, leaving only a dynamic stage management using the statusbar.

Subtypes have been updated :
- new: stage_id.sequence=1
- stage changed: stage_id changed, not new
- user assigned: when user_id is set

Misc:
- [IMP] views accordingly;
- [IMP] reports accordingly, added date_last_stage_update in reports;
- [IMP] subtypes
- [REM] [REF] [TESTS] removed some tests because they are not applicable anymore; rewrite some tests and moved some of them into unittests
- [DOC] doc directory + changelog + stage explanation in project and project_issue;
- [REM] removed project.task.reevaluate wizard

bzr revid: tde@openerp.com-20130719094706-ea0hbwjj99pochzo

1 files changed, 1 insertions, 41 deletions

diff --git a/addons/project_issue/test/issue_process.yml b/addons/project_issue/test/issue_process.yml
index afb68a9b6c2..280df50ebea 100644
--- a/addons/project_issue/test/issue_process.yml
+++ b/addons/project_issue/test/issue_process.yml
@@ -1,24 +1,4 @@
 -
-  In order to test process of issue tracking in OpenERP, I Open the Issue.
--
-  !python {model: project.issue}: |
-    self.case_open(cr, uid, [ref("crm_case_buginaccountsmodule0")])
-- 
-  I check state of Issue after opened it.
-- 
-  !assert {model: project.issue, id: crm_case_buginaccountsmodule0, severity: error, string: Issue should be in open state}:
-    - state == 'open'       
-- 
-  Now I put Issue in pending due to need more information.
-- 
-  !python {model: project.issue}: |
-    self.case_pending(cr, uid, [ref("crm_case_buginaccountsmodule0")])
-- 
-  I check state after put in pending.
--  
-  !assert {model: project.issue, id: crm_case_buginaccountsmodule0, severity: error, string: Issue should be in pending state}:
-    - state == 'pending'
--
   I send mail to get more details. TODO revert mail.mail to mail.compose.message (conversion to customer should be automatic).
 -
   !python {model: mail.mail }: |
@@ -29,29 +9,9 @@
         new_id = self.create(cr, uid, {'email_from': 'support@mycompany.com','email_to': 'Robert_Adersen@yahoo.com', 'subject': 'Regarding error in account module we nees more details'})
         self.send_mail(cr, uid, [new_id], context=ctx)
     except Exception, e:
-        pass  
--
-  After getting sufficient details, I re-open Issue from pending state.
--
-  !python {model: project.issue}: |
-    self.case_open(cr, uid, [ref("crm_case_buginaccountsmodule0")])
--
-  I check state of Issue after re-opened.
--
-  !assert {model: project.issue, id: crm_case_buginaccountsmodule0, severity: error, string: Issue should be in open state}:
-    - state == 'open'   
+        pass
 -
   I create Task for Issue.
 -
   !python {model: project.issue}: |
     self.convert_issue_task(cr, uid, [ref("crm_case_buginaccountsmodule0")])
--
-  I close Issue after resolving it
--
-  !python {model: project.issue}: |
-    self.case_close(cr, uid, [ref("crm_case_buginaccountsmodule0")])
--  
-  I Check state of Issue after closed.
-- 
-  !assert {model: project.issue, id: crm_case_buginaccountsmodule0, severity: error, string: Issue should be in done state}:
-    - state == 'done'