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


Ignore:
Timestamp:
09/20/21 13:43:03 (4 months ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Requests/2.0

    v23 v24  
    1616
    1717== Requirements ==
     18* REQ should only have a single Requests system, for which the req_need model is currently more suitable.
    1819* REQ & INV should both be able to operate without the other
    1920 * This is currently the case & shouldn't get broken by this restructure
     
    4849
    4950== Phase 2 ==
    50 * REQ should only have a single Requests system, for which the req_need model is more suitable.
    51 * req_req should be stripped down to it's logistics core usecase & moved to inv_req
     51* req_req should be stripped down to it's logistics core usecase
    5252 * Remove types (so remove support for Simple, Skills, etc)
     53 * Remove current req_skill/req_commit_person/req_commit_skill models
     54
     55== Phase 3 ==
     56* Move req_req to inv_req
    5357 * 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
    5458 * Also move associated !Controllers/Classes/Functions/View
    55  * Remove current req_skill/req_commit_person/req_commit_skill models
    56  * req_job commented until Phase 3
     59
     60* req_job commented until Phase 4
    5761
    5862=== Pros ===
     
    6468* Still have 2 separate Requests systems
    6569
    66 == Phase 3 ==
     70== Phase 4 ==
    6771Move req_need (& associated tables) to CCC template (SHARE is already isolated now).
    6872