-
Notifications
You must be signed in to change notification settings - Fork 0
AnA12S03AllowDeleteOrderElements
Jeroen Baten edited this page Mar 9, 2018
·
1 revision
TWiki>
LibrePlan Web>AnA12S03AllowDeleteOrderElements (05 Nov 2012, ManuelRego)EditAttach
| Story summary | Allow Delete Order Elements From Web Services |
| Iteration | AnA12WebServices |
| FEA | AnA12S03AllowDeleteOrderElements |
| Story Lead | |
| Next Story | |
| Passed acceptance test | No |
The behavior of the DELETE operation in LibrePlan that will be implemented will be the next one:
- It will delete the order element in the WBS and all its associated configuration: criteria requirements, label assignments, progress measurements, quality forms and material requirements.
- It will delete the task in the planning if the order element to remove is a planning point or if it is an ancestor of a planning point.
- It will erase the incoming dependencies to the task in the Gantt and the outgoing dependencies too.
- If the order element to remove in the WBS has children elements (it is a WBS container), the service will delete them in cascade.
- If the order element to delete is inside a container and is its only child, we will convert the container in an order line. A container cannot be empty, it has to have always inner tasks.
- If the order element to delete is the project order (the root WBS element) all the project will be removed.
As validation condition, the DELETE order web service will throw an error message in the order element to delete or one of its children has time tracked (work hours have been tallied as devoted or) or expenses.
| Tasks | Est | Spent | To do | Risk | Reviewer | Developer | Task Name | Start Date | Est End Date | End Date |
|---|---|---|---|---|---|---|---|---|---|---|
| Task | 7 | 7 | 0 | Low | ManuelRego | ManuelRego | Add delete operation for order elements from web services |
Copyright (c) by the contributing authors. All material on this collaboration platform is the property of the contributing authors.