[FR]: Make context entries clickable links

[trdischat]

Feature Category

None

Problem Statement

I am trying to use the context field to track the person, if any, that a task relates to. I regularly create notes for people. So I want to put a note link into the context field. This works reasonably well. If I enter [[Joe Smith]] in the context field, it gets stored correctly as a clickable link in the task note properties. But the Task View, Kanban View, etc, display this as @JoeSmith and it is not a link.

Proposed Solution

I have a slight preference to retain spaces in the context name, but could live with the CamelCase version of the text. The key improvement would be for @JoeSmith or @Joe Smith to be a link that is clickable in the same way that projects currently work.

Use Case Examples

I use this for people as context, but this could also apply to places and other types of context where having a note with information about that context is useful. Another advantage to having a note page for a person is the ability to create a table on the person note page listing all tasks for which that person is a context. I do this currently with dataview or datacore, but you could also use Bases or a TaskNotes widget like the one that already exists for projects. All of this works already without the requested enhancement, but it would be more convenient if I could link directly to the person page from the task in the Task List or Kanban Views.

Priority/Impact

Medium - This would be a nice improvement

Additional Context

No response

[callumalpass]

Thanks for the suggestion here @trdischat. My intention has been for "context" to be a plain-text field. The parsing logic of "projects" is quite complicated, and may be difficult to replicate for contexts, but I'll have a think about what we can do!

[renatomen]

hI @trdischat and @callumalpass
My two cents: Whenever we implement triggers like @ to select from a list of items, I suggest we let users define triggers of their preference, like I did with the "Status".

Some people would prefer ^ for people, others would prefer ^for context or even !...
Considering that this is in the "capturing" process which needs to be frictionless, forcing user to use a trigger that they dislike can be a significant friction...

[callumalpass]

Thank you for reporting this. This should be resolved in release 4.8.0, so I am going to close this issue now.