Changes between Version 23 and Version 24 of BluePrint/Requests/2.0

Timestamp:

09/20/21 13:43:03 (3 years ago)

Author:

Fran Boon

Comment:

--

BluePrint/Requests/2.0

@@ -16 +16 @@
 
 == Requirements ==
+* REQ should only have a single Requests system, for which the req_need model is currently more suitable.
 * REQ & INV should both be able to operate without the other
  * This is currently the case & shouldn't get broken by this restructure
@@ -48 +49 @@
 
 == Phase 2 ==
-* REQ should only have a single Requests system, for which the req_need model is more suitable.
-* req_req should be stripped down to it's logistics core usecase & moved to inv_req
+* req_req should be stripped down to it's logistics core usecase
  * Remove types (so remove support for Simple, Skills, etc)
+ * Remove current req_skill/req_commit_person/req_commit_skill models
+
+== Phase 3 ==
+* Move req_req to inv_req
  * Similarly req_req_item/req_commit/req_commit_item/req_approver/req_req_tag/req_order_item/req_project_req should be moved to inv_req_item/inv_commit /inv_commit_item/inv_req_tag/inv_req_approver/inv_req_item_order/inv_req_project
  * Also move associated !Controllers/Classes/Functions/View
- * Remove current req_skill/req_commit_person/req_commit_skill models
- * req_job commented until Phase 3
+
+* req_job commented until Phase 4
 
 === Pros ===
@@ -64 +68 @@
 * Still have 2 separate Requests systems
 
-== Phase 3 ==
+== Phase 4 ==
 Move req_need (& associated tables) to CCC template (SHARE is already isolated now).