+2
Qualified

Associate Attachment from a different project from a task

Brad McClure 1 year ago in Productivity Management updated by Mike Lewis 9 months ago 3

Similar to the functionality of allowing users to select a specific digital asset in a task to associate to the project, I would like to allow the user to be able to select an attachment that was previously uploaded to the activity and limited by project visibility to associated to the project they are working on via the task. This would reduce clicks, duplicate attachments and provide a much better user experience. I do not think that the feature needs to allow for attachments associated to other activities to be visible. I would recommend that only the attachments that are limited by specific projects be selectable (activity level attachments already would appear). I would also like this to be a feature that is administratively controlled like digital assets in the workflow administrator, but if there is a better way to manage this we are open.

Talked about this with Eric Teitsma today, clarified the ask here is to make it easier for users to associate attachments to a project/workflow within a task. Would like for the ability to see all assets associated to the activity with the same asset type so users could associate within the task (or upload window) vs. having to navigate to the attachments page.

Qualified

So are you asking that there is almost another document location option?  Instead of upload or URL, etc there is also a "Existing Activity Attachment" option?  When selected the user can see all the attachment for the activity and pick a document from that list.  When they select it that document has its settings changed to make it visible to that project?

If this is the use case, why use project visibility at all?  Can you not just have the attachments visible to all projects?  I assume there must be a reason that does not work?

sorry for the delay on this. I lost track of this one.

I would think that it would be more of an Existing Project Attachment option.  Obviously if it's an attachment at the activity level, it's automatically visible at the project level.  This is more of the case where we have users that need the same attachment to show up in specific multiple workflows. For example.  We have creative projects and approval projects. Users should be leveraging the integrated approval process within the creative process.  However, many times they do not which causes them to upload the same document a 2nd time into the approval project because they don't know how to associate the attachment to a different project. If instead of forcing a new upload, we could give them the option to select an attachment that is limited to another project that would limit the duplicate attachments, and seamlessly associate the  annotations to the attachment and make them visible across the appropriate projects. We can't move the attachments to the activity level because there are multiple projects happening at once.

There are other use cases we have where user error isn't the reason, that I can share if you need.