[Status: Launched! 🚀] Move Attachments

Hi, Not only move but to link it with or copy it to another task/folder...

It would save space and produce happy customers :)

Hello,

An example would be a policy that required development. As different tasks are created for the review and approval, the current version of a Word document containing the policy could be advanced from one task to another seamlessly.

I think this would be a great feature too. Please can you add it :D

This would be so helpful. For example, i project manage an in-house creative team. It would be great if I could move or easily access the attachments that a designer posts so that I could attach them to a new task for a client to see and approve. Currently, I have to download them from one task and upload them to the next. Seems like it could be easier.

This, and the ability to share an attachment between tasks would be great as well; in our workflow we've found that one document (i.e. pdf) is often referenced/used in multiple tasks and projects. We often end up having 5 identical uploads - one would suffice...

I think it a necessity. An online tool with the potential of Wrike should have a drag and drop interface. My own example meant downloading and saving files and then re-uploading to 26 discreet tasks. Such a facility would greatly increase user experience, lower download upload/bandwidth and storage used

It definitely is a necessity to be able to link an attachment (file) to multiple tasks. As far as I understand, the reduction of redundancy is one of the main purposes of working with Wrike. Speaking of reduction of redundancy: it needs to be possible to merge two tasks or put one task in another one (as subtask) as well.

I've just had one of my team upload attachments into the wrong task, so I would find it ideal if I could select them all and choose a 'Move' action where I can choose which task to dump them into

I have the same use case as Sherri. We chose Wrike, in part, because of the ability to add files to a review. It would be great if the final version of a file from internal review task could be shared or added to a client review task without having to upload it a second time (similar to how a task or project can be shared to multiple folders).

Agree! The ability to link multiple tasks to one source file would be super helpful. This is one of the strengths of a system like Airtable. It would be nice to see Wrike move more toward an asset management model where files are just files and then tasks can point to them (and then remove the reference). This would make the original request much easier. Need to move? Unlink, then Re-link in another task. Or the other way, go to a file and tell it which tasks to be connected to.

This functionality would be amazing an an incredibly useful feature for our business. I often find that we are linking the same document/file to multiple tasks. It's not an effective use of space and can sometimes cause confusion if one doc is updated and another is not. 

Also, the use case for using Google Drive does not work for our organisation. We all use Google Drive however our security policy does not allow users external to our company access, therefore we cannot link to a document in Google Drive and share with a customer/collaborator. 

Would love an update on whether or not this feature is being reviewed?

I agree with everyone above -- we use Wrike forms to gather information to start a marketing project, and our form has space for attachments (images, any previously written copy, etc.). It would be ideal to be able to move those files to the actual task I create from those request forms. Please add this functionality!

Addendum: I downloaded the attachments from the request form, had to extract the files because they were automatically zipped, relocate the files to OneDrive (which pops up in a window almost entirely off my screen), and choose those files from OneDrive. I've gone through the attaching process three times and they still are not showing up. This is a testament to how much time your users would save with the added functionality!

I have 'liked' this thread! Any chance there is an update to whether or not this is possible to move files from one task to another? 

This drag and drop feature is a must add - wasted time having to download and reupload 

Would also be great to simply take a new file that was uploaded and then be able add as a new version; an example is team members do not always follow process and they upload a new file version but not to the file currently in review.  Then one needs to download and reupload as a new version in order for it to be captured in the review and have the history of versions viewable in proofing tool

This drag and drop feature is a must add - wasted time having to download and reupload 

Would also be great to simply take a new file that was uploaded and then be able add as a new version; an example is team members do not always follow process and they upload a new file version but not to the file currently in review.  Then one needs to download and reupload as a new version in order for it to be captured in the review and have the history of versions viewable in proofing tool

Elaine Lisa Looks like this just passed 60 upvotes! Looking forward to hearing back. This would be such a beneficial feature. 

Hey Christopher Halkovic and everyone, our Product team should be providing this thread with a status soon. As soon as I have one for you, I'll let you know!

Thank you, Hugh! Looking forward to it. 

Thanks. 

Hey everybody, just received an update from the Product team. This suggestion is planned to be implemented and they are currently researching the idea. I've added the status of "Investigating" to the thread, and as soon as I have another update for you, I'll let you know! 😊

This is wonderful news, Hugh!! This is going to save so much time. One question though, will this support moving from the project level down to the task level? For instance, when we receive a project through a Wrike request form, it would be ideal to have the ability to move from the project level down to the task level. 

Our team works on projects that are updated annually for internal clients, using PDFs that we mark-up and tasks for team members to complete. Our problem stems from using a different PDF for each discrete task. We begin with a "content" task starting with last year's document, mark that PDF up, create a version history, then when the issues are resolved, upload a version of the PDF to a NEW task—the "design" task, starting a second version history. When the design task is complete, we upload versions of the PDF to a third and often fourth task, creating new version histories. When the job is ready to print, we upload a potential fifth version of the PDF into a new task, creating yet another version history. When tagging each other in tasks, we are expected to work in one version history—say a "review" task—but then go backwards to upload a revised PDF to the "design" task. This job flow is creating frustration among team members, fractured version histories, and confusion. Is there a "best practices" job flow we can use, connecting a single PDF and its single version history to multiple tasks? Thank you for your insight.

Hey Christopher Halkovic, moving between projects and tasks is currently planned as well 😊

Hi Beamish, thank you for your use case! Sharing a single file's history across tasks is not currently possible in Wrike. I would recommend making another Product Feedback thread to suggest this as a possible new feature. Once that thread reaches 60 upvotes, our Product team will be able to provide it with a status.

If you have any other questions, let me know!

Good day,

I hope you all are staying safe!

Is there an update from the production team Hugh?

Cheers!

Hi Norm Barrette, hope you're staying safe too!

The Product team is continuing to research this suggestion. As soon as I have more information in regards to the status of this thread, I'll be sure to let you know.

@... just to add to what has already been said. We use Wrike to manage project process for a creative team (internal retail company agency) and will have projects setup like the following as an example:

1. Copy Development Round 1
2. Internal Review 1
3. Copy Development Round 2
4. Client Review 1
5. Copy Development Round 3
6. Internal Review 2
7. Copy Development Round 4
8. Client Review 2
9. Finalization of Copy

This example is for copy, but could be for any type of document creation (Word Doc, Photoshop file, etc). As these are seperate tasks, the file needs to be uploaded, edited with version control, then downloaded, and re-uploaded as a new file and version to the next tasks. This obviously defeats the purpose of the version control and makes the file management messy. 

Marc Foster, I called in to Wrike and was told that one task per pdf is best practice. The tech with whom I spoke suggested using subtasks branching off the task containing the document to accomplish what had been listed as tasks to help maintain version control.

I hadn't been familiar with subtasks before, but will be bringing them to the attention of my team.

Beamish yes we have tried the sub-task approach but its just a good one as it causes the Gantt view to get really messy with dependencies going all over the place vs being more sequential.

I really hope they solve this soon.