Ability to @-mention other tasks in a task description in project template

Hello Everyone,

I hit a small roadblock in a template I use. The template is composed of many tasks. In some task description, I need to link (with the @) other tasks.
HOWEVER (here comes the trouble)
When I create a new project with the template, the links in the task descriptions are referred to the template, and not to the new project.

EXAMPLE
Template 1

  • Task 1
  • Task 2 (in the description the link is to Template 1-Task 1)

New Project (Created from Template 1)

  • Task 1
  • Task 2 (in the description the link is STILL to Template 1-Task 1, and not to New Project-Task 1)

Do any of you know how to overcome this?

Thanks
Carlo

2 Likes

@Carlo I did some testing of your issue and came up with the same problem. I think the problem is that the @mention identifies the task I.D. number and whether you duplicate the project or go the template route I think it is still going to duplicate the ID of the template. Maybe somebody else can figure it out. Sorry

1 Like

Hi @James_Carl
Thanks for the comment

You are right when you say that it is the ID which links the specific task. I was hoping that being a template, it was using the assumption that all the tasks and the links inside the template itself would be linked to the “implementation” of the template…

@Carlo I think your observation is a very worthy observation and should be suggested as an improvement. For instance, dependent tasks seem to hold their relevant project. I think solution would have to be if the task mention is inside the project it switches to the new project, if outside the project stays the same.

2 Likes

Hi @Carlo, has anybody suggested this observation as an improvement?

1 Like

If you want this to become a product request you need to move the thread to the product feedback category of the forum so people can upvote it.

Thanks Bastien,

I do not know how to do it.
Can you help me?

I’ll let @Marie confirm that we can

@Bastien_Siebman / @Marie - I’m experiencing this issue 2 years later, so I’m assuming there haven’t been any updates. Was the thread ever moved to the product feedback so we can upvote? If so, could either of you provide the link?

Thanks!

1 Like

Same issue here as well. Other than task dependencies I’m not sure how to create a workaround. Task dependencies aren’t really the same and are not the functionality I want to create.

1 Like

Same issue for me too, is there a fix in work as it would be amazing to have tasks linked to the next one in some way but I’m having the same issue as the original poster from 2019.

1 Like

I would also love this capability to link between tasks in templates, not just using dependencies!

you mean a link like Jira does, with different flavours beyond the simple blocked/blocking?

I haven’t used Jira project templates, so I’m not sure. But yes, what I want to be able to do is have Task A, Task B, and Task C within my project template. Within the description of Task C, I want to be able to mention Task A or Task B.

I know I can use dependencies to link the tasks, but sometimes a dependency isn’t actually the relationship I want to reference.

For example, I have a training that gets run repeatedly. I make a template project for running the training. I have a milestone task that contains all the key information about a session. In other tasks, new information gets decided about the session, and as a step, I want the person handling that task to add that information to the milestone task.

Right now, I have to set the milestone as “dependent” on this other task, and then within the description write something like “Update the session milestone task, linked as a Dependency”

That’s fine as a workaround, sure. But IMO it would be cleaner if I could just @ the task I want them to click on.

Understood, sorry I was confused by the name of the thread I did not realise we were discussing @-mention, I renamed the thread!