Allow screenshots in updates/comments

Thank you. Can I add a screenshot via email versus being in the system? Our team is very much used to being able to copy and paste a excel table, document, or image into a comment from an email notification, so what is the best practice for all these scenarios in WF?

@mcintke Hi, this has been in place for a while now, the Idea has been marked as Delivered.

When in an Update, you can attach an image-format screenshot, you can even copy/paste an image in your comment without having to save it as a file first.

NOTE: You need to ensure your instance has this enabled in Setup in order to utilize this - Go to Setup > Interface > Update Feeds > Preferences

Is this happening?

This has been delivered.

Hey @madalyn_destafney This is an interesting suggestion and one that I am open to. Let's discuss this during our call later this week, and I will discuss adding it into our process moving forward.

Hi @jon_chen , based on the new Ideas process. Would it be possible for advisors to be able to change Idea status as we go thru these to be able to mark things as Delivered that have been implemented, like this one? It would also be really helpful to be able to filter Ideas based on status or by specific timeframe, right now we can only sort by old/new/most likes/views.

@anna_asatryan , I must have thought you were replying to my comment but thanks for the reply. I will send in a ticket although support had previously said I would have to send that in as a feature request/idea.

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

@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.