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

48
45 comments
Spot On Innovative Approach Stellar Advice
Avatar

+1

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

👍

0
Comment actions Permalink
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

0
Comment actions Permalink
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 ☹️

 

0
Comment actions Permalink
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

0
Comment actions Permalink
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.

 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Linking a task with # yes please. +1

1
Comment actions Permalink
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
Comment actions Permalink
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.

1
Comment actions Permalink
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.

0
Comment actions Permalink
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
Comment actions Permalink
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
Comment actions Permalink
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)

0
Comment actions Permalink
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
Comment actions Permalink
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
Comment actions Permalink

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

Top
Didn’t find what you were looking for? Write new post