Custom Field Type: Doc
Elaine Tse
Now that we can @@@Docs, it'd be great to be able to also link Docs to a task via a custom field. This would be similar to the Tasks custom field type, but for Docs.
Log In
Caroline Ginty
open
Hi all - updating this Status as of March 2023. I'd also love to know more about the use case(s) this would unlock for you/your teams to make sure we are prioritizing effectively. Thanks!
Elaine Tse
Caroline Ginty: for me it would be useful to have the Doc link in list view. We might have a custom field for "tech specs" or "release/training notes", and having these links as custom fields just makes it easier for users to find them rather than searching through the task description for a link. It would be an easy way to see if we have completed creating these docs for each task. Additionally, since Docs and Custom Fields can be permissioned such that they are hidden from guest users, we can use this as a way to link internal documentation that we don't want to expose to our client guest users without them seeing an inaccessible link. For example, we might not want to expose "tech specs" to our clients.
Caroline Ginty
Elaine Tse: Definitely makes sense! Have you played around with the 'Linked Docs' column in List view? This likely wouldn't solve for you Guest user use case since this column is not a Custom Field (so doesn't have a 'Visible to Guests' setting), but at least could help you highlight your docs at a glance from List view!
Elaine Tse
Caroline Ginty: Thanks for highlighting this! I didn't know about this, but just tested it out. I added a doc reference via @@@doc in a task description, and then viewed the task from a list view which had the linked docs column added, but it shows empty. It seems like I have to add the task link from the doc in order for this column to populate. It's workable, but it's several extra clicks that I think our end users would easily miss.
Caroline Ginty
Elaine Tse: Agreed - thanks for testing it out and I think we can definitely make this easier! cc Justin Hunter/Ivan Villa maybe there's a quick win here we could enable with Doc/Task linkage.
Justin Hunter
Caroline Ginty: Agreed! This is aligned with a similar thread on the relationship between tasks and docs here: https://clickup.canny.io/feature-requests/p/tasks-created-in-docs-set-reference-pointanchor-in-the-doc-where-the-task-exists
Jake Hopkins
Also important for me. We can link documents as a built-in column, but I now use ClickUp tasks to put out contract calls / bids, and often need technical specs and similar documents attached in a clean presentation and accessible to any via a public link.
There are workarounds of course, but having custom fields tap into Docs and be publicly distributable changes the presentation game (for me, anyway).
Nicola Taylor
I'd love this to be able to link our SOPs (created in docs) to the tasks they're associated with. At the moment I can @@@ link to include them in each task individually but in order to audit whether all of our tasks have an SOP attached we need a column in a list or table view. Right now we're just using a URL field but a direct link in Clickup would be a lot neater.
Bill
Hi, I think the superior solution would just be to include reciprocal @mentions like you guys already do in tasks when one is mentioned in another. The Custom Field for tasks I think was just a stop-gap for you guys to the ultimate field that you now have as a sort of "non dependent" dependency, where both tasks "mirror" each other when linked.
Thanks!
Christophe Marchand
It would also help to have access to docs related to certains tasks easily.
Andrew Bixler
This would allow me to also remove Dropbox Paper from the list of tools that I use. I could track a task and the associated doc with it in one place.
Ivan Villa
planned
Jamila Payne
Ivan Villa: I would like to take the fields from a form response and embed them in a document. So that If a form view captures first name in a document I could add <FIRST NAME> and it would automatically populate everywhere in the document that <FIRST NAME> is placed. Basically, pulling custom fields from a form into the document.
Ivan Villa
Jamila Payne: Hi Jamila! We have seem similar requests to this one, look up merge fields or dynamic fields and you will find a few more from fellow ClickUppers. We are looking at creating doc templates, which could play nice with a feature like this :)
Jamila Payne
Ivan Villa: Thanks I'll take a look. To clarify, I would want these fields to populate in to a document template that I create. The fields would not always be basic like <FIRST NAME> but might in be <ANSWER TO CUSTOM FIELD #1> I would like to option to put ANY custom fields that were created for a form into a doc. Hope that helps.
S
Staffing Supply Chain
Ivan Villa: Any chance you know what the timing is on this planned improvement? Would be great to be able to pull in custom fields to the doc or doc template. Thanks