Adobe Workfront General

When users are "auto-provisioned" through SSO, they are created with the base access level (Requestor) by default. This base level is the requester access. There is currently no way to change the default, this is a limitation of the product. I'd like a way, as an admin, to change the default access level to Reviewer instead of Requester.

This is just a test I have a customer that needs to edit their idea and I am trying to find out how to do so.

Workfront should allow aggregations on calculated fields in a report (or any other column in a list view). For example, right now, if three people are assigned to a task, you can aggregate the cost of their labor based on their role cost per hour or user cost per hour. But in many consulting firms, users work across multiple roles and make a percentage of the billing rate for that role on that work. Right now, there is no way within Workfront to aggregate labor cost for tasks assigned to multiple people that may be making different percentages of the billable rate.

The Mark as Read dot is pretty small. Can we have a bigger target to click on?

Please allow the option for when a user is tagged within a form the user then receives an automated email. This is critical if we need the specific user to be aware they have been added to the form to work as a notification.

As a System Administrator/Integration Specialist I need to be able to diagnose Event Subscription failures through the Workfront API. When a event subscription has a failure, there is nothing available within the Event Subscription API to determine what caused the failure. It would be great if whenever a failure is returned, the error code and message is provided.

When working in a very large project (hundreds of tasks), it can become a chore to constantly scroll down through phases where there are many parent tasks where all the child tasks are complete. Using a filter to only show Open/Incomplete tasks isn't ideal as you lose visibility of the project structure and phase gates. It would be ideal to have a setting which would allow you to turn on "Auto collapse Parent Tasks when all Child Tasks are complete". This will clean up the task list a lot, and also still give nice visibility in a Gantt view.

Most users log time directly to the project or task as they complete work items, but our leadership logs time on a much broader scale to projects that are really just "time tracking buckets". Sometimes they may work the same hours on the same projects for weeks at a time. It would be great to be able to simply copy week 1's timesheet hours into week 2's timesheet w/o the need to manually enter in each hour.

Some of our project tasks are always assigned to the Project Owner, Project Sponsor, or Resource Manager. I'd love to have a solution that allows me to put a rule in my Project Templates for the Assignments field... something like "$$projectOwner" that would automatically assign that task to the project's owner each time I use that template.

We are in the process of migrating our appx 1.000 users to NWE. What we noticed is, that it would be easier to copy already configured NWE layout templates and adapt them instead of using the Classic Templates where we would need to add all the settings that are new in the NWE.According to our support engineer, the mapping between a classic layout template and the corresponding one in the NWE is done via the ID. So it would be a great feature if we could either manually map a specific NWE template to a Classic one (so users migrated would receive that NWE template) or manually set the ID on the NWE template to match whichever Classic template we would like.

It would be awesome if we could calculate the time difference between 2+ objects in a project. For example in my report I have the "converted issue entry date" and the "project actual start date", because these are two different object types and the issue likely sat idle for some time in the queue before a PM converted it to a project, I want to be able to see what that idle time was by calculating the difference between the project actual start date minus the converted issue entry date.

Instead of having to add a custom task reminder at an individual task level, allow it to be part of every project settings on default. Make this an email notification option to select in a user's profile to receive or not receive these notifications.

Would be beneficial if Workflow templates could be added more than once to a Workflow for instance.A default template where all options are setup so the user does not have to change any stage settings apart from the stage name, add some users to it and then choose the same template from the Add Template dropdown menu to add another stage.Currently this doesn't work and reports that the template has already been added to the proof, even when deleting the stage added by the template and trying to add it again causes the same error.So if you delete template stage from the workflow it should be removed from the proof.

The ability to prevent certain Users, User Groups or Teams from unlocking Proofing Stages would be helpful, we are forever correcting proofing workflow stages that have been unlocked but never relocked by the user causing the document to show in multiple reports and not just the correct report.Even educating users does not prevent this and this is what most of our time is spent doing.

Need the ability to change integration visibility based on group permissions so that all users do not see the entire list of Document integration links and only see the ones that apply to them.

Ability to customize the Requests Template/Layout. For example, we'd like to add the name of the requester to the Header of requests. Or, we'd like to be able to include information from the form on the updates tab of the request layout. More flexibility on where you can place things within the layout of a submitted request.

Just like you can click on a layout template to see who is assigned to it, it would be great to do this for job roles for users AND to see easily if the job role is used in any project templates. When scrubbing job roles and templates, it's impossible to know easily if any roles aren't even in use so they can be deleted. Also helpful to know for revising project templates if you change a role for task(s) assignments, what templates use the old role so can be easily swapped to new role.

Similar to how a project cannot be marked complete unless all requests/tasks under it are not completed. it would be really helpful if we can apply same logic to stop users from closing programs unless all open projects are marked closed.

Having the ability for Text Mode Columns to be sorted by either ASC or DESC is a must, currently Text Mode Columns are not sortable, the querysort parameter doesn't work for Text Mode Columns.

We would like the ability to Automatically lock all active stages in a Workflow when a user who has the Email Alert of Decisions makes their decision on that proof.Current example is we have Project Managers and Stakeholders who are connected to different proof stages on a document, the Project Manager should be allowed to make the final decision, even if no user on the Stakeholder stage has made their decision causing the active Stakeholder stage to be locked.

I have tried all the samples on the forum but still unable to merge / sharecol multiple columns into one for reporting.

I was recently asked to provide Workfront's Authentication requirements to our security team. I went to the setup page and was able to see some of them. However it doesn't show the requirement for length of password. That can be found by requiring someone to reset their password, then going to that setup page. But for admin knowledge it would be nice to have all the authentication requirements listed in one place. Even if we cant change them.

Currently the hasNotes feature of a Document Version reports notes that are added across all versions of a proof even if there is 3 versions.It would be good if there was also a way to check for notes added only to the current version and again report True/False.

It seems that the only way for the "Is Ready" flag to get turned on with a Kanban board is to physically drag an item out of the Backlog. If a developer clicks into something from the backlog and changes the status to "In Progress", the item disappears from the board. Please add a setting to default "Is Ready" to "Yes" for all incoming work to a Kanban team.

There has been a lot of confusion on my team about the purpose of the "Send Work Request" button within our Kanban Board. Developers expect to use this as a quick way to add tasks to the board, however this button was apparently built to create "personal tasks", so the work request never actually makes it to the board. Instead, it goes to a new project called "[Developer's Name]'s Tasks". This isn't helpful for us, as we would expect those requests to go to the project associated to the Kanban board. The ability to select a project when using this button would help clear up these issues.