Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.

What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders...

Hotlink to other tasks from within conversation.

10 comments

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Nihad Perva

    this was a feature once they introduced the @ in comments but was stripped, i guess it generated performance problems

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Blair Lierman

    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.

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Turner McCulley

    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.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Nihad Perva

    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

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Anastasia

    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.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Kristian Koch

    So I'm not suffering Alzheimer's. I knew I'd seen this working before... 

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Stephanie Westbrook

    @Kistian definitely not! 

    Stephanie Westbrook Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Philip Rikli

    We're also very much missing the feature. Vote up if you agree and maybe it'll come back... Thanks!

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Frank Canova

    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.

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Nihad Perva

     @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

    Is this helpful? 0
    Comment actions Permalink

Please sign in to leave a comment.

Folllowing List for Post: Hotlink to other tasks from within conversation.
[this list is visible for admins and agents only]

Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.