Content
View differences
Updated by Oliver Günther about 4 years ago
**Sketch**
* Request /api/v3/work\_packages with filter (precedes = \[current WPID\])
* This gives us the finish date of the preceeding relationships, from which we calculate the latest date
* Improve performance with signalling (<mention class="mention" data-id="42565" data-type="work_package" data-text="#42565">#42565</mention>)
* Request /api/v3/work\_packages with filter (follows = \[current WPID\])
* This gives us the information if any following WPs will be updated, and if so which one
* We get the parent/children information from the embedded information
* From this data, we can construct the banner message.
**Limitations**
* We might not be able to see why certain dates are blocked / limited due to lack of visibility
* TBD: Use undisclosed feature of (project?) ancestors for showing there is a relation even if it is not visible. This does not work with the above approach right now, unless the API can give us undisclosed filtered values.
* Request /api/v3/work\_packages with filter (precedes = \[current WPID\])
* This gives us the finish date of the preceeding relationships, from which we calculate the latest date
* Improve performance with signalling (<mention class="mention" data-id="42565" data-type="work_package" data-text="#42565">#42565</mention>)
* Request /api/v3/work\_packages with filter (follows = \[current WPID\])
* This gives us the information if any following WPs will be updated, and if so which one
* We get the parent/children information from the embedded information
* From this data, we can construct the banner message.
**Limitations**
* We might not be able to see why certain dates are blocked / limited due to lack of visibility
* TBD: Use undisclosed feature of (project?) ancestors for showing there is a relation even if it is not visible. This does not work with the above approach right now, unless the API can give us undisclosed filtered values.