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).

Find more posts tagged with

Launched

Status: Launched

Comments

Elizaveta Bogdanova

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 🙂

Daniel Paul

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.

Juan Muttoni

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 🙂

Andrew Moore

This is really important for us, too!

Elizaveta Bogdanova

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 🙂

Kaori Murayama

this is important for me too. i just upvoted.

Eric Perche

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):

{
            "id": "IEAFL755KQ7PR3PG",
            "title": "Our task",
            "responsibleIds": ["KUAO5H6E","KUAO5H6F"],
            "responsiblePlaceholderIds": ["IEAFL755NMAAINMT"]
}

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):


{
            "id": "IEAFL755KQ7PR4PG",
            "title": "Our task",
            "responsibleIdsWithAllocation": [
                {
                    "id": "KUAO5H6E",
                    "effortAllocation": 60
                },
                {
                    "id": "KUAO5H6F",
                    "effortAllocation": 180
                }
            ],
            "responsiblePlaceholderIdsWithAllocation": [
                {
                    "id": "IEAFL755NMAAINMT",
                    "effortAllocation": 120
                }
             ]
}

Elizaveta Bogdanova

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 🙂

Scott Taft

This is important for us too. Need a way to see effortAllocation by assignee when Effort is in flexible mode

Juan Muttoni

Hi @Scott Taft, thank you for adding your support, I've passed your comment on to our relevant team 👍

Andrea Calvi

and? Guys, yuo can't just say: I've passed it on and that's it. Give us some feedback. Is it going to be implemented? Is it a priority? When can we expect it?

Juan Muttoni

Hi @Andrea Calvi, welcome to the Community. I'm afraid that this suggestion has a lower number of votes, and this feature isn't on the current roadmap. If you'd like to learn more about how we process feedback, feel free to check this article.

If you have any additional questions, please let us know 👍

Scott Taft

Hey there @[Deleted User] how soon do you think this item will receive a status now that it hit 60 upvotes?

CC: @Monika Mandi @Daniel Paul @Andrew Moore @Kaori Murayama @Eric Perche @Andrea Calvi

Rohan V

Hey @Scott Taft 👋

Thank you for flagging the lack of status.

Our team is aware of this and is aiming to implement this feature by the end of the year. We've added the "Coming soon" status to this post. Rest assured, I will keep you updated as soon as I have more info on this 👍

In the meantime, let me know if I can help you with anything else. Thanks!

Scott Taft

Hello, has there been any update on the status of this feature?

Basudha Sakshyarika

Hi @Scott Taft! 🙋🏻‍♀️ The API for flexible effort has been released, and the documentation can be found here.