Add the context property to all object types
The addition of the super flexible "Context" field on Tasks should get wider use. For example I would love to add "context" to the Weblinks I save but I am limited to doing this with Tags which don't come with the structured data of other objects. Please consider adding context to... everything?!
7 Comments
Sign in to comment
I love the context, and my entire schema in Tana was built through context links and recursive searches. I can create a custom text field and link contexts, but what is incredibly useful about the task context is that it only gives predefined object types.
Is there an alternative to either give the option of linking multiple object types to the Object type field (a request elsewhere?) or create a free-form field that allows you to link to any object type but limits the input only to previously defined objects?
+1 – then: I think this is identical to this.
(… correct me if I am wrong 🙂)
Add the context property to all object types
(… correct me if I am wrong 🙂)
This would be a HUGE advancement. Right now we are limited to individual Object lookup properties, but it gets unmanageable when you need to link People, Organizations, Projects, Weblinks, Pages, together.
As things stand, the context property will remain a feature for tasks only.
The context property is just a different way of displaying backlinks which we built custom for tasks based on how we wanted task management to work in Capacities.
Whilst we understand the request, we are hesitant to add it because that would mean introducing new ways to think about backlinking which increases the complexity of the product.
It also only works for objects, not blocks and linking in blocks is an important part of creating connections.
I agree, the context field is super useful and should be available for custom objects as well!
I add a custom text field called "Links" to every object and then link with @ObjectType/ObjectName, but I *REALLY* like the ease of the Context field.
Since context is a feature of tasks only then it really needs to set its context automatically when duplicating an item.
If I want to duplicate a task that is in say a project I have created, and if I didn't see the "Context field", I have no idea where the duplicate went and if it in fact was created in the first place. In general anytime you duplicate anything the context should always be the originating object by default. This provides the user visual feedback that the request actually worked.