Done
Details
Assignee
Craig McNallyCraig McNallyReporter
Piotr KalashukPiotr KalashukTester Assignee
Craig McNallyCraig McNallyPriority
P2Story Points
1Sprint
NoneDevelopment Team
ThunderjetFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Craig McNally
Craig McNallyReporter
Piotr Kalashuk
Piotr KalashukTester Assignee
Craig McNally
Craig McNallyPriority
Story Points
1
Sprint
None
Development Team
Thunderjet
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created July 30, 2019 at 7:50 AM
Updated August 5, 2019 at 3:58 PM
Resolved August 5, 2019 at 3:58 PM
Overview:
Given our change in direction wrt acquisition unit assignments, we no longer need separate APIs/views/etc. for managing acquisition unit assignments for orders
This effectively "undoes" the work done previously in MODORDSTOR-92, MODORDSTOR-94, MODORDSTOR-95, MODORDSTOR-96 and MODORDERS-266
Approach
Typically we wouldn't just remove APIs that have already been released, but given that it's highly unlikely that anyone has started using these APIs yet, that's how we're going to proceed here...
Remove the APIs from:
RAML
ModuleDescriptor
Code
Acceptance Criteria:
The APIs are removed
The View is removed
Unit tests are updated