[Question/Feature Request]: task dependencies in /tasks endpoints

[timkley]

What is your question?

Currently it is not possible to know if a task can be started without doing a series of API calls:

• get the task from somewhere (either /task/{id} or maybe from /me/projecttasks...)
• get the tasks dependencies via /tasks/{id}/taskdependencies
• get each task and check their status (should be done)

I'd propose a feature to simplify this. Either by loading the dependency relationship for each task (could be quite expensive I recon) or by providing another attribute similar to, for example, isCompletelyScheduled. This attribute could be named isStartable.

These approaches may be a bit to naive since its not possible to depict all possible combinations of statuses the predecessors could be in. I'm also open for a simpler approach without doesn't need a few hundred API calls to find out if a task can be started :)

Do you have a trace id of the call?

No response

[nilzzzzzz]

Hi @timkley ,

we have right now no cool way to make it easier for you to calculate this. The only way to improve the logic and to do less calls is to apply this logic per project. The task & dependencies endpoints are available in that scope.

I marked you proposal internally as improvement. Thanks for you detailled feeback.

Nils