API need to show Flexible effort allocated by assignees.
Now API doesn't show Flexible effort allocated by assignees. However, you can still use the GET/tasks/{taskId} endpoint with fields=["effortAllocation"] parameter to check total allocated effort.
I used the following query in my test account to get this information: GET/ https://www.wrike.com/api/v4/tasks/IEADG63PKQYWBF4C?fields=["effortAllocation
Could you please extend with the developers somewhere-somehow the mentioned API with this information?
To get back an array instead of just an object which contains the relevant informations (effort allocated by assignees, mode, total effort, percentage).
Welcome to the Community, Monika Mandi 👋 Thanks a lot for sharing this feedback, I'm passing it on to the team now. Here's a post that explains how we work with Product Feedback; please let me know if you have any questions!
If you'd like to know what this Community has to offer, please check out our New to Community forum 🙂
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Hi Lisa,
we have the same problem here. We need the all effortAllocation per day and task. But the Wrike PAI have no endpoint to get this information. This post ist from 2022, you have some news for us about this feature reqeust?
Thanks a lot.
Hi Daniel Paul, welcome to the Community! I have opened a ticket with our Support Team so that one of our experts can provide you with an accurate reply, you will be contacted very soon 👍
Allow me to mention that you can visit our New to Community forum to get the most out of your experience with our Community 🙂
Juan Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Juan Wrike Team member Become a Wrike expert with Wrike Discover
This is really important for us, too!
Thank you for supporting this suggestion Andrew Moore, and welcome to the Community 👋 If you'd like to check out what these forums have to offer, I'd highly recommend our New to Community forum 🙂
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
this is important for me too. i just upvoted.
Really key for us.
Alternative proposal would be to make 2 new options in the Enum of the "fields" parameter to keep the API backward compatible with existing integrations:
Today we can use in the request: fields=[responsibleIds,responsiblePlaceholderIds]
Getting back such a json (removed some fields to make it shorter as example):
We might get new request parameters to get the outcome more complete: fields=[responsibleIdsWithAllocation,responsiblePlaceholderIdsWithAllocation]
Getting back a json like this one for instance (shorter for same reason):
Hi Kaori Murayama, Eric Perche, welcome to the Community 👋
Thank you both for sharing your feedback, I'll now pass it on to our team responsible for API.
Be sure to let me know if you need help with anything else 🙂
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover