Allow screenshots in updates/comments

[#1]

Please let us add screenshots to comments or updates, as in JIRA. These images do not need to be revision-controlled, like a document, but we need to be able to easily share images within the team, and would prefer to stop using email or OneNote for this purpose.

[#2]

@Manish Singh

I tried to message you directly but I kept getting an error.

Hey Manish,

I wanted to let you know that I have been able to drag and drop images into the updates section from Snagit by pulling them from the thumbnail view in Snagit to the Update. It saves me from having to save it to my desktop and then upload. Hope that helps!

[#3]

@Manish Singh

I tried to message you directly but I kept getting an error.

Hey Manish,

I wanted to let you know that I have been able to drag and drop images into the updates section from Snagit by pulling them from the thumbnail view in Snagit to the Update. It saves me from having to save it to my desktop and then upload. Hope that helps!

[#4]

@Tara McKinnon

That works fine for SnagIt users as SnagIt technically saves the images to disk in its library. Tools like Windows Snipping Tool and the freeware image capture tools don't do this and store it to the clipboard.

For this to be fully functional and be a workflow consistent with competitive products, it needs to be able to accept images from the clipboard.

Hopeful that WF Product team is still watching these discussions as I'd think most of us would only agree that this is partially delivered and needs to be clearly identified where it is on the roadmap.

[#5]

@Tara McKinnon

‚

You are right. It works for SnagIt but as @Jeff Wunderler pointed, other products like Greenshot and Windows snipping tool doesn't pick the image from clipboard. Hopefully, Workfront will add this feature in the future releases.

‚

I wasn't aware that it worked for SnagIt 🙂

Thanks!

[#6]

@Tara McKinnon

‚

You are right. It works for SnagIt but as @Jeff Wunderler pointed, other products like Greenshot and Windows snipping tool doesn't pick the image from clipboard. Hopefully, Workfront will add this feature in the future releases.

‚

I wasn't aware that it worked for SnagIt 🙂

Thanks!

[#7]

Any updates on finishing this project by implementing the ability to paste (ctrl+v) an image from the clipboard vs having to attach from a file on the OS?

[#8]

Workfront implemented this incorrectly. We've limited some of our users (group A) from reading update threads/seeing documents where they are not specifically tagged. What workfront did was these images on updates was much like documents and so when the user adds an image to the update where group A was tagged, they still don't see the image because the image is a document and is not shared specifically to group A! And there's no way to change the sharing permissions of the image to allow group A to see it! The function needs to be corrected so that the document (image) on the updates inherit permissions based on who is already in the thread.

[#9]

Hi @CustomerSu ,

You should be able to enable the image attachment functionality from your instance from Setup -> Interface-> Update Feeds -> Preferences .

Let me know if that worked or if you have any questions.

[#10]

@Anna_Asatryan , we already Allow users to add images in updates. However, Workfront did not take into account the access level setting (never inherit document access form projects, tasks, issues, etc) and since the image added to the updates area is considered as a document, the user who has this restriction would not see that image in the updates even if they're specifically tagged in the thread. AND there is no button to give this user access to see that image/document in the thread. While Workfront did follow through with the restriction, there's no option to change the access.

In the documents section in a project, the user requester has access to the project but does not inherit the project permission and so documents in the project would have to be shared specifically to the user requester. That way, any internal documents can remain internal even if the requester has access to the project.

[#11]

Hi @PollyCo ,

Apologies for the irrelevant comment. I was typing a message on several similar messages and posted a wrong one here. 

Have you submitted a support request? If no, please do, so that we could take a closer look at this with the development team.

Kind regards,

Anna