[Status: Backburner ⌛️] @Linking to projects/tasks

+1

👍

Reading through the thread this feels like we're beating a dead horse, but another example of where this would be SUPER useful is in managing requirements traceability matrices and change logs. If i want to track an original requirement (or a new requirement) to the change log, I have no way of including a link or more information for tasked references. 

Upvote x 10, please

Agree, upvote x 1000 please, wee need this for meetings 😤

@Wrike is almost there, so why not compleate the work?

If not by using @then use the + add to folder/projects

...it is possible to add to project or folder, but when trying to link to a specific task or sub task or sub sub task then it don't ☹️

Hey there, everyone! Thanks a lot for your feedback here, and it's good to see it's getting more popular too! More upvotes would definitely help our team see just how many of you would like this to be implemented. Please don't forget to +1 the original suggestion! I'll be back here in Q1 2020 and hopefully be able to share some good news 🙂

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, despite my cynicism I haven't fully given up on coming back to Wrike, in particular as my license is paid up for many months still.  

I would put this issue as one of the examples I have been presenting as how you guys handle your roadmap:

- 60 vote number is arbitrary, seems like a way to justify to the community not moving on requests.  This is a big one, very old, has 40 votes, and is a fundamental feature of a quality Project Management App.  You guys are 1/2 to having the feature since you can already nicely unfurl tasks in description and comment canvas, and you can search for other other tasks with auto-complete in the subtask view.  So all you need to do is allow the ability, like Asana has, to search for the tasks with say an @mention, and then display its link as you do with unfurling.

With that complete, if you could just add to the "@mentioned" task the reference in the other task, you have completed this feature and made a ton of users happy!

- 2nd point:  You said in your last post you'd be back in Q1 2020.  Did you really intend to?  There are 6 days left!  And I can just see what you are going to say..."sorry guys, talked to the Product team, we have no update...oh and if you want to find out more about how we handle requests, here's a link to our policy..." 

I do not intend to be obnoxious, but you guys bring this on yourselves and could easily prove me wrong by changing your approach to one that's more transparent (like connecting your weekly Release Notes - which are nice I have to say - to the actual community requests), and stop repeating the same comment in different words, which basically insults users' intelligence at this point.  I'd rather hear that "no this is not going to happen for the next 2 yrs because we are preoccupied with a new UI, speed improvements, Wrike for Marketers, catering to the Professional Services niche " or whatever it is.  

I do sincerely hope to see movement on the 10 or so threads I'm following to this day with equally unhappy users, it would do a lot to change my thinking about you guys.

Linking a task with # yes please. +1

Hey everyone, thanks for your feedback here!

Sorry for the delay in getting back to you here. I've checked with the team, and for now, they aren't planning to work on this in the nearest future. I'll continue to pass on your feedback and use-cases, and once I have an update from the Product team, I'll make sure to let you know! 

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

Coming from Jira this is a HUGE deficiency in the software. Even better than @ a task would be to have a link type and the ability to link them. Dependencies are great, but rarely covers everything.

In our team we would like to use such links in custom fields as well. My example is duplicate tasks.

User1 opens some task, lets call it Task A

User2 opens a new but basically the same task, lets call it Task B

I would like to close Task B with an appropriate 'Canceled' type of status/resolution, and link Task B to Task A in the custom field.

That way anyone that opens Task B for any reason can easy see that it's a dupe and Task A is where they should capture any new information.

Thanks for providing your feedback Judah Ferst Miguel B 🙌

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

Wanted to add my continued request for this feature.  You guys have this already available in subtasks, a lot of modern apps have "/" commands or other ways to pull from in-app content into Rich Text fields, so really hoping you guys can bring this to fruition soon since you're 1/2 way there already with the subtask functionality!

Would really appreciate this feature. I use this often in Asana and would appreciate a similar behavior. (@mention a task/project/folder and link directly to that task)

Hi Al Sape, Jason Nehez, I've asked the team to provide an update here, so I'll let you know once I hear back from them! 

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

Ok thanks Lisa.  While I'm not expecting you to say anything but "I need to check with the product team," I just can't say enough how baffling it is to observe how these requests are handled internally:

- You guys have a team of mods, yourself and a few others, who have to "check" with product just about every time you respond in here.  What is "Product?"  Do you guys have such poor communication internally that you can't just see enough of the roadmap to see what you're working on at Wrike and report back in a respectful way to the community, instead of "sorry there's a Chinese Wall between you users and those actually building the product, let me find out what they're working on" to paraphrase.  I mean, do you actually use Wrike, which is supposed to alleviate poor communication within teams?

- Whatever you are working on bigger picture is not transparent to the community.  You have some vague status on a number of requests.  These are user-generated requests, so we can't be sure if you're actually working on them as written by the user, or you simply tag them as "under consideration" to appease the community.  I've seen many releases that didn't really line up well with the requests, but you guys considered those requests "launched."

- There is no timeline on any of the statuses.  I mean nothing whatsoever.  Something in "back burner" could be staying there perpetually for all we know

- You constantly release features not anywhere mentioned in the boards.  Where is the public visibility of those?  Is there any reason, given the primarily negative feedback in most of the requests around here, not to present a view of what you guys ARE actually working on fully transparently?  And not just tag some requests as "coming soon," leaving us to guess how much of that represents the work you are actually doing?  And as a consequence, provide actual true transparency as to why many of these features are being ignored?  If you published even with limited detail some information about what you're working on, it would be much easier to tolerate these requests that are getting bypassed, because we could actually see why.  When you simply write every few months "sorry, Product can't do that now" it belittles your correspondent.

I am just one user voicing dissatisfaction for long over a year now, so I doubt this will do much to change your approach, and I have resolved to be frustrated.  But it isn't easy to come back to this product, pay for a license, while ou seeing how you have not changed at all with the way you treat the community as valued customers deserving transparency and honesty in exchange for thoughtfully provided, valuable feedback.

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

@linking of tasks with reciprocal visibility would take Wrike to the next level!  Jira is fantastic for abilities to link and cross connect tasks.  

Thank you for sharing your feedback Aaron! 🙂

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 also think this would be hugely beneficial. Having to click into another project, copy the permalink, then input that into the task is unnecessarily time consuming. 

Hi Laura Walz, thank you for adding your support here! Please be sure to upvote the original suggestion if you haven't yet 🙋🏻‍♀️

Being able to search for and link to a task, folder, or project via the "@" tag search feature would save SOOOO much time! I copy and paste an insane amount of permalinks every day (into descriptions and comments), and I know most of my teammates do as well. Lisa Does this idea have enough votes now to be considered for feature development? 🙏

Thank you for reaching out and supporting here Daisy Hibbard 👍 The team is interested in this idea but doesn't have this planned in the short term. We'll continue passing the feedback and vote-count here to them regularly.

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

Please consider that this is also a hard forum to come across. I'm also really frustrated that cross-linking tasks isn't easier, and it also took me a while to find the right search term to even discover this forum...so I'm sure MANY users are also frustrated by this but just aren't alerting your team

Agreed. BASIC functionality and the main reason why we're evaluating other products. Even more frustrating, there are multiple instances of this same request that should be consolidated - assuming they care about these requests enough to read and organize them, that is. Here are just two I've come across:

https://help.wrike.com/hc/en-us/community/posts/115003384329-Feature-Request-Automatically-add-task-references-to-comment-stream-of-referenced-tasks

https://help.wrike.com/hc/en-us/community/posts/360037418634-Backwards-Links

Samantha Finken Welcome to the Community 👋 Thanks a lot for supporting this idea and also for sharing your feedback on how our Product Feedback forum works 🤗 We're always reviewing ways to improve your Community experience. 

Ellen Nunes Thank you for throwing your support here also 🙌 In relation to the similar posts in this forum - we can't merge them here, but we do consolidate feedback internally and report on it to the Product team.

If you're interested to see what Community suggestions have been launched in 2021, please check out this post 👍

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 really should be taken off of the backburner.  The link capabilties are obviously there in the database, since I can copy and past a link and it instantly "transforms" to a live link with title.  It takes significant time when taking meeting minutes, or creating a dashboard to search, copy link, paste, etc.  This is by far the hardest issue to work around.  We all want @ mentions and direct links! 😀  Google Docs, Asana, Notion, Jira, etc. all use this methodology.

Thank you Aaron! We'll let you know here if we have an update 👍

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

+1 Reviving this for 2023.