[REM] project_issue: Remove module, merge into project.task

3 files changed, 0 insertions, 89 deletions

diff --git a/addons/project_issue/doc/changelog.rst b/addons/project_issue/doc/changelog.rst
deleted file mode 100644
index e74516f1600..00000000000
--- a/addons/project_issue/doc/changelog.rst
+++ /dev/null
@@ -1,13 +0,0 @@
-.. _changelog:
-
-Changelog
-=========
-
-`trunk (saas-2)`
-----------------
-
-- Stage/state update
-
-  - ``project.issue``: removed inheritance from ``base_stage`` class and removed
-    ``state`` field. Added ``date_last_stage_update`` field holding last stage_id
-    modification. Updated reports.
diff --git a/addons/project_issue/doc/index.rst b/addons/project_issue/doc/index.rst
deleted file mode 100644
index 9e12eef2124..00000000000
--- a/addons/project_issue/doc/index.rst
+++ /dev/null
@@ -1,22 +0,0 @@
-=====================
-Project Issue DevDoc
-=====================
-
-Project Issue module documentation
-===================================
-
-Documentation topics
-''''''''''''''''''''
-
-.. toctree::
-   :maxdepth: 1
-   
-   stage_status.rst
-
-Changelog
-'''''''''
-
-.. toctree::
-   :maxdepth: 1
-
-   changelog.rst
diff --git a/addons/project_issue/doc/stage_status.rst b/addons/project_issue/doc/stage_status.rst
deleted file mode 100644
index 6afd4508cd9..00000000000
--- a/addons/project_issue/doc/stage_status.rst
+++ /dev/null
@@ -1,54 +0,0 @@
-.. _stage_status:
-
-Stage and Status
-================
-
-.. versionchanged:: 8.0 saas-2 state/stage cleaning
-
-Stage
-+++++
-
-This revision removed the concept of state on project.issue objects. The ``state``
-field has been totally removed and replaced by stages, using ``stage_id``. The
-following models are impacted:
-
- - ``project.issue`` now use only stages. However a convention still exists about
-   'New' stage. An issue is consdered as ``new`` when it has the following
-   properties:
-
-   - ``stage_id and stage_id.sequence = 1``
-
- - ``project.task.type`` do not have any ``state`` field anymore. 
- - ``project.issue.report`` do not have any ``state`` field anymore. 
-
-By default a newly created issue is in a new stage. It means that it will
-fetch the stage having ``sequence = 1``. Stage mangement is done using the
-kanban view or the clikable statusbar. It is not done using buttons anymore.
-
-Stage analysis
-++++++++++++++
-
-Stage analysis can be performed using the newly introduced ``date_last_stage_update``
-datetime field. This field is updated everytime ``stage_id`` is updated.
-
-``project.issue.report`` model also uses the ``date_last_stage_update`` field.
-This allows to group and analyse the time spend in the various stages.
-
-Open / Assignation date
-+++++++++++++++++++++++
-
-The ``date_open`` field meaning has been updated. It is now set when the ``user_id``
-(responsible) is set. It is therefore the assignation date.
-
-Subtypes
-++++++++
-
-The following subtypes are triggered on ``project.issue``:
-
- - ``mt_issue_new``: new tasks. Condition: ``obj.stage_id and obj.stage_id.sequence == 1``
- - ``mt_issue_stage``: stage changed. Condition: ``obj.stage_id and obj.stage_id.sequence != 1``
- - ``mt_issue_assigned``: user assigned. condition: ``obj.user_id and obj.user_id.id``
- - ``mt_issue_blocked``: kanban state blocked. Condition: ``obj.kanban_state == 'blocked'``
-
-Those subtypes are also available on the ``project.project`` model and are used
-for the auto subscription.