Describe the feature:
It would be cool if GET /_tasks/<taskid> could support a list of task ids (i.e., comma separated or as a request body).
My use case here is to avoid using the detailed parameter together with the actions parameter, which may cause detailed information to be gathered for quite a few running tasks, which according to the docs can be expensive. So I'd like to target the detailed usage to just a specific subset of tasks. Rather than issuing a request per tasks, I'd like to issue a single request with a list of tasks.
Describe the feature:
It would be cool if
GET /_tasks/<taskid>could support a list of task ids (i.e., comma separated or as a request body).My use case here is to avoid using the
detailedparameter together with theactionsparameter, which may cause detailed information to be gathered for quite a few running tasks, which according to the docs can be expensive. So I'd like to target thedetailedusage to just a specific subset of tasks. Rather than issuing a request per tasks, I'd like to issue a single request with a list of tasks.