Sharing a document across tasks

Our team frequently works through PDFs, adding issues w/in a PDF, marking those issues 'resolved,' uploading subsequent versions, and double-checking changes through the version history. 

Our issues come from having to upload redundant versions of a PDF into separate tasks, to assign tasks to individual team members. This breaks the versioning history, generates emails alerting team members to changes on threads assigned to others, resulting in frustration, and multiple unconnected version histories. 

Hugh suggested I start a new thread to suggest improved functionality allowing the sharing of a single PDF (or Word doc, etc) across multiple tasks, allowing for a single unbroken version history, and allowing for tagging through email to direct users to tasks assigned to them, rather than directing them to tasks assigned to others.

60 upvotes are needed before the product team will assign this crucial functionality will receive a status. Please comment if this functionality would help your team communicate more effectively through Wrike. 

4
5 comments
Spot On Innovative Approach Stellar Advice
Avatar

Hugh, from a "best practice" perspective, would it be better to attach PDFs (or other docs used collaboratively by multiple team members at the project level, rather than uploading them within a task? I suppose this would still be problematic re: email notifications directing users to a task where they'd still need to go up-and-out to get to the document where the issues are tagged....

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

This would be great. I think the current functionality would support linking to a single file from a different system (like Google Drive) but that gets clunky and we have issues maintaining those spaces already. If we could just upload files and then access them from various tasks, it would definitely help. Voting now!

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hey everyone!

Beamish, thank you for creating a separate post for this, I'll move it to our Product Feedback forum (that's where community members vote for different feature suggestions) - hope you don't mind! 🙂

As for best practice, you could attach the files to projects, but if there are multiple files, I'd suggest having a separate task for each file. You could also look at the Approvals feature that helps organizing your review process. Please let me know if you have any questions! 

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thanks Lisa, 
I don't mind at all. 

You mentioned a separate task for each file. Our issue is multiple tasks containing different versions of the same file, each with a different version history with multiple "issues." We often top 100 "issues" in single rounds of changes, and sometimes have 100 issues in one round on one task, and 100 issues in another round in another task, then 20-30 in yet another task.

This simply cannot be a best practice. It's a bit of a mess. I'm hoping by allowing one document to be linked to multiple tasks, we can at least limit the versioning history and the hundreds of issues within a single document. 

Perhaps you're suggesting we should have one task per document? Would tagging users in subtasks be a potential solution?

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hey again, Beamish! Yes, that's what I meant - one task per document, and subtasks should be helpful too to tag different team members. I also mentioned Approvals above - they help you organize the review process for your team. Plus, there's also Proofing that allows you to add comments directly to images, videos, .pdf and Microsoft Office files attached to tasks, folders, and projects - this might be helpful if your team review multiple files. 

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink

Folllowing List for Post: Sharing a document across tasks
[this list is visible for admins and agents only]

Didn’t find what you were looking for? Write new post