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

One feature I miss from Asana is being able to directly link to tasks/projects using the @ symbol. It's a big pain point having to load the project or task in another window to get the link.

Upvote 68
52 commentaires
Spot On Innovative Approach Stellar Advice
Avatar

+1

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

👍

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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 ☹️

 

2
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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.

 

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

Linking a task with # yes please. +1

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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

0
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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.

2
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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.

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

Thanks for providing your feedback Judah Ferst [OD] 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

0
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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!

0
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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)

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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

0
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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.

0
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar
Hi Al Sape! This suggestion isn't currently on the roadmap for this year, unfortunately. I understand that you'd like to know why this is so and, while we don't currently provide a publicly available roadmap, the reason for this is that the team will be focusing on other features and functionality. For example, one of the team's big focuses this year is going to be the continuous improvement of the New Wrike Experience, among other priorities.
 
We regularly check with the Product team to see if there are any updates on feature requests, as we need to ensure we're sharing the latest news and any relevant detail in relation to the request.
 
This forum is one of our feedback channels. If you have a Customer Success Manager, it's also possible to leave your feedback with them, or with our Support team, who can also help with letting our Product team know your improvement suggestions. The team reviews all the feedback from these channels, as well as from surveys, in-app feedback, interviews etc., and makes decisions on what to implement based on these insights. While this is the case, I totally understand how frustrating it can be to see that your suggestion isn't planned here, but your voice still gets heard and we thank you hugely for sharing your thoughts with us. Wrike comes as an out-of-box solution and the team can't commit to being able to respond to every idea that they receive, but they still review all the suggestions and feedback shared.
 
Please rest assured that we do want to provide you with more info, and for that reason, we're planning to work on our overall feedback process. We aim to be more transparent on timelines in the future. We appreciate you raising the points you have here. Thanks for your contributions on the Community, your feedback, and your eagerness to support various suggestions.
 

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

0
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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

1
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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

0
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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. 

2
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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

Cansu Community Team at Wrike Wrike Product Manager En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online

Cansu Wrike Team member En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online

0
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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? 🙏

2
Actions pour les commentaires Permalien
Spot On Innovative Approach Stellar Advice
Avatar

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

0
Actions pour les commentaires Permalien

Folllowing List for Post: [Status: Backburner ⌛️] @Linking to projects/tasks
[this list is visible for admins and agents only]

Haut de la page
Didn’t find what you were looking for? Write new post