Hotlink to other tasks from within conversation.
In the same way that you can @mention another user and bring that user into a conversation, sometimes in the comments, it is useful to be able to point to other tasks that have info pertinent to the conversation.
It would be good to be able to auto-link to existing tasks while making comments.
this was a feature once they introduced the @ in comments but was stripped, i guess it generated performance problems
I agree that this would be a very useful ability. I was talking with a co-worker today about this and he also thought it would be incredibly helpful to not have to grab the link (usually in another tab) for a task while writing a comment in a different task.
GitHub has a very similar functionality, it uses the '#' character to reference other issues and pull requests. This separates it from @mentions, but allows a quick way to cross-reference other issues or PRs in descriptions and comments.
I would find this feature very useful. I often need to open another tab to pull the permalink to the task to include it in a comment.
as i already wrote, it was available in the beginning and they stripped it because it created too much overhead and too few users have used it, that was the argument that they told me when i asked for it
Hi everyone, thanks for commenting here and sharing your thoughts! @Nihad, that's absolutely right, this functionality existed previously bt was discontinued to enhance Workspace performance. That said, thank you for adding this request to the Community, it's helpful to learn about which functionality is/isn't helpful for different teams.
So I'm not suffering Alzheimer's. I knew I'd seen this working before...
@Kistian definitely not!
We're also very much missing the feature. Vote up if you agree and maybe it'll come back... Thanks!
We're trying to use Wrike for SW tasks, and @Mention to another related task is essential in our comments. Copying/pasting permalinks is the only work-around we found but it's too cumbersome to use in practice. I agree with @Blair 's comment, if Github has figured out a way to make this work, the Wrike team can as well. Using the # prefix instead of @ is a perfectly acceptable alternative if it helps.
@frank i would also suggest the same as it looks that this feature would be used by a minority the @implementation in the first place created the problem because it began to get slow in bigger installations where there are 10 of thousands of tasks and even if you just want to mention a colleague it had to read through all the tasks, if you seperate those it should not have any performance hit for the casual user and the # could intelligently first show active and recently modified tasks and only read more if you confirm it in the hitbox