[Status: Not planned] Create Task from Microsoft Teams Message
We'd love to have the ability to create a task in Wrike from a Microsoft Teams message the same way we can from an email in Microsoft Outlook. As we use the Wrike/Teams integration more, this feature would be really useful.
We appreciate your support here, folks! I'll let our team know about your interest here.
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
I looked for this as a standard 'Workflows' in Teams, and came up empty. A quick Google search landed me here.
+1 for requested.
This would be a great addition. In my case, I want the ability to create a Task in my Personal Space from a Teams Channel Post and/or Teams Chat Post. I do not believe having a custom Request Form is a good solution for this need.
We moved from Teams/Planner to Wrike and we are really missing the ease of making a task in Wrike seamlessly from Teams. Please consider adding this functionality.
I figured that this can be achieved by created a message extension in Teams which calls a task create action using the Wrike API. The problem here is that Microsoft use the OpenAPI standard to easily create these API calls and Wrike does not have an OpenAPI Description Document for the Wrike API. While I'm sure developers can find a way around this to trigger Wrike API requests from teams, the easiest way is for Wrike to publish an OpenAPI Description Document to make it fairly straightforward for anyone to create the message extension in Teams. Please consider this alternative if there are no plans to develop this integration feature natively.
Hi everyone 👋 Thank you for sharing your views, feedback, and support for the suggestion. As of today, there are no further updates for this year. If there is any progress in the upcoming months, I will be sure to let you know 👍
Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Rohan V Wrike Team member Become a Wrike expert with Wrike Discover
Well, that's hugely disappointing.
Over 2.5 years after the initial request and nearly 100 up-votes later, and nothing. What's the point of having this feedback system? Are the product managers at Wrike even looking at these suggestions? So disappointing.
Seriously. Its wild that you don't have this feature on your roadmap. I upvoted this 2 years ago, I've been watching comments come in the whole time. And there has been zero movement in this. The Thank you posts from the support staff are now getting to the point of insulting.
Hi folks! We understand it's disappointing to see no updates for this suggestion. I'd like to confirm that our team has been receiving all feedback from this thread and we're keeping a close eye here.
Kim Batina I'd say it makes sense to participate as every year several Community suggestions become Wrike features. Here's an example from last year - you'll see the list of Community suggestions that had been released in 2023 (and we'll create a similar post for 2024 soon too).
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
Rohan V Lisa Having a community suggestion open for more than 2.5 years is a problem especially that there is no clear mechanism for putting the idea back into investigation by the product team. According to this post on guidelines and statuses related to product feedback, the [Not Planned] status seems to be a very vaguely worded 'end state'. What's the point of upvoting, commenting on, or waiting for an update on a suggestion with "Not Planned" status when its obviously been placed in the trash bin by the product team? I suggest changing the status to "Rejected" and closing it for any further input from the community instead of keeping us all here waiting for Godot!
For the time being I will start a new suggestion for this feature with some selected texts from this thread. I hope that everyone who's upvoted here do the same on the new suggestion to get it to the 60 votes needed to go into evaluation again by the product team.
Here is the new suggestion, please upvote!
Hi Hassan Mourad ! 🙋🏻♀️
Thank you for taking the time to create a new post and share more details. The status "Not planned" refers to not being planned for the near future. However, this doesn’t mean it lacks the potential for future implementation. The team will definitely revisit the post(s) if they start working on this or anything similar.
I hope this makes sense. Thank you again! 😊
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Basudha Sakshyarika Wrike Team member Become a Wrike expert with Wrike Discover
Hello Basudha Sakshyarika, thank you for your reply. Its unfortunate that my new post about this feature has been marked as "Duplicate" and we are back to this one. All we know is a suggestion can stay for years in the "Not Planned" status. You say, "the team will definitely revisit the post if they start working on it or anything similar", that's great to know, but it still doesn't tell us how the community input can influence the team to revisit the post! Does the number of upvotes still count for anything? if so, what is the threshold? Is the team triggered by the number of comments? or maybe the content of the comments, if say, someone makes a good suggestion in the comments? I still don't see the point of this "Not Planned" status and keeping the community engaged without any clarity on how our continued engagement matters.
Lisa is there any update? This is a very important feature.
I guess a better question we could ask since they don't seem to find value in developing this feature, is how does Wrike currently recommend end users quickly accomplish this task without the integration? Surely if this isn't planned yet, there is a valid work around that isn't just copy and pasting the message over to Wrike's website/App.
Adam Whetham see my post above about using API to do this. of course with some challenges.
We are honestly soon getting more bug reports, updates and service requests through Teams than email or other channels. This would be a huge addition for us too. I would imagine there's a lot more use in other chat based communication apps as well.
We definitely need this ASAP, it could be very helpfull for our company, please put this into your roadmap
Hi everyone! 😊
Thank you for your feedback and suggestions. I understand how important it is to see this suggestion implemented. Please know that our team carefully evaluates all input to assess feasibility and prioritize effectively. Regarding this particular suggestion, the team will review it during the planning for next year. I will surely keep you updated with any news in the coming months.
Thanks again for sharing your thoughts!
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Basudha Sakshyarika Wrike Team member Become a Wrike expert with Wrike Discover
I support this feature
Just started an enterprise account and this feature would make our work flow so much more seamlessly! Please consider for the near future!
Our team also needs this feature.
I don't think the product managers at Wrike care about what the customer wants. It's only been 3 years and 105 votes so far. Perhaps it might be on the roadmap in another 3 years? What will it take? Grrr.
Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Rohan V Wrike Team member Become a Wrike expert with Wrike Discover
We would also love this feature, I can't think of many other features that would save as much time as create a task from part of a teams chat. I can send that section of the chat to outlook or Jira. Really want to send it to Wrike.
Why is this not being developed? It's so simple, you've already built it for Outlook - just do the same thing for Teams. We've just migrated from Trello, but this is a key function that's missing.
We've managed to build a custom integration to have this function on teams. I still think this should be an out of the box feature and very disappointing that the Wrike team chooses to ignore this request for more than 3 years. I'll be asking my dev team to document the steps we did and will post it here to guide anyone who would like to DIY it.
Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Rohan V Wrike Team member Become a Wrike expert with Wrike Discover