Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

KnoahPiNew Participant

Remove existing user from Updates/comments thread?New

It would be VERY helpful if we had the ability to REMOVE users from the distribution/notification/inclusion list of an existing Updates/comments thread within WF.This would help b/c there are times when we want to retain the history of the conversation while continuing that conversation only with a smaller group of people than those people who were tagged within that thread early in that thread's lifecycle. I am aware that a new Update/comments thread can be started within that same area on WF, but that can be confusing for some of our users and frankly it makes finding historical elements of a conversation sloppy.This would also help b/c we have people in our organization who get accidentally tagged on a thread which they should not be on and the notifications that they receive can be very annoying to them if they're not relevant. We then need to make a choice to either start a new thread without that person which means that the historicals of the conversation are then less accessible to the folks who need it (OR) we choose to continue the conversation with that person tagged on it and continue to annoy them but retain the historicals. We often choose the route of keeping the person who should be removed on the thread so that we don't lose the historicals but that annoyance that results becomes a deterrent for WF adoption in our org.If/when this is added, it should be done in such a way that is not easy to accidentally remove someone.Thank you!

MaryPieTFCU
MaryPieTFCUNew Participant

Agile Scrum BoardNew

Description - Currently the Scrum Board only shows tasks assigned to a Team.  I want to see two different scrum boards.      1. BY TEAM:  A board to show tasks assigned to anyone on that team.  This will allow resource assignment to tasks to team members while seeing everything else they are assigned to on all issues and projects.  Changes to tasks on a project can be restricted to that project owner, but during team meetings that persons full allocation would be understood and planned.        b. BY PROJECT:  A board to show tasks within a project.  New tasks go into the project backlog.  This will allow projects to managed in a agile fashion without being built in a waterfall project plan.  When a task is assigned to a resource, it would be on the project agile board, but also appear on that person's team board.  Project tasks can be planned at the project level on this board.  Burndown chart should show velocity for all iterations of the project and predict project end date based on velocity and remaining tasks.   Both of these Agile boards should have the ability to drag and drop tasks to and from the Backlog, and between current Iterations or future Iterations.  This will allow iteration planning without jumping between screens and views, so iteration planning meetings will go faster and feel less cumbersome.  

jdrurka1New Participant

Document Drag-and-Drop should fire a document change event for the Event Subscription APINew

Description: Workfront uses the Event Subscription API to transmit changes to our services when a document in created or updated on a project. Currently, when a file is moved (drag-and-drop) from one folder to another, it does not fire any event to indicate that this action occurred. The argument i got from support was that this just "changes the folderID field 'on' a document", and that their product was functioning as intended. However, changing the folder ID for a document is in fact a change TO the document, as you are changing critical information associated directly with the document. In computers, a file/document always exists within a folder. When you change where the document lives, in computer operating systems and workfront, it is always done by doing operations on the file icon itself, or specifying the file's path and/or name. Thus, it makes sense that changing the folder a document is in should be an notable enough be considered an "UPDATE" event in the Events Subscription API.   Why is this feature important to you: This feature will be used heavily by the Marketing department at our University. Documents will be initially created in a "Campaign Notes" folder, and will later need to be transferred into a "Finalized Files" folder. After the transfer to Finalized Files, an event should be fired to our services that downloads said folder into storage in our University's infrastructure. It is necessary that an event fires to signify that an existing file was moved into that folder.   How would you like the feature to work: When any document is drag-and-dropped between folders in a Workfront project, a Document UPDATE event should be sent using the Event Subscription API described in following link: https://experienceleague.adobe.com/docs/workfront/using/adobe-workfront-api/event-subscriptions/event-subs-api.html?lang=en   Current Behaviour: Currently, UPDATE events are only sent when a new version is uploaded from an external source, and CREATE is only sent when a new document is uploaded from an external source. As an upload is simply a "move" operation from an external source into workfront, I'm not sure why the same logic wouldn't apply to fire an event for "moves" of the file within workfront, also.