For those using Scrum Teams, what kind of access does the Team have to the task or source project?  It seems Contribute access to the task does not allow the Scrum team members to add Stories (Tasks) to an Iteration.  Giving them manage access to the Task allows them to change anything on the Task.

Another suggestion is to create a filter on the Project screen so you can filter on this screen without having to create a report. 

@Sven-iX  is correct.  I suspect that if you have only used 1 milestone path for all other projects, that your new projects may be at the bottom of the list or on a next page if you 2000+ projects.If you build a report, then you can add a filter for Project > Milestone ID = X.

For anyone who is using Kanban within the Boards module > I am curious to know what issues or limitations you've experience with the Boards module.   We currently using Teams for both Scrum and Kanban teams, but are looking into transition Kanban to Boards.  Any insight or wisdom is greatly apprecia...

I dont believe this is possible.  This is something that would be really helpful for our teams. To work around this, we created a multiselect custom field and gave the Scrum Master access to edit the field so they could add new tags as needed.  We then created a view with that field as one of the co...

Try text mode with the following when the resolving object id is a task. displayname=Ownertextmode=truevaluefield=resolveTask:project:owner:namevalueformat=HTML

Try using Resolve Project > Owner ID fieldThen switch to text mode and change all the "ID" to ":name"         

Seeking to learn how others managed the rollout of the Unified Experience for Workfront from their end users experience.  How did you communicate the change to your users?Did the removal of branding become an issue?Did the UI pose any challenges to the users?Any lessons learned that we should levera...

We are trying to build a report that pulls projects where a user has manage access, but is not necessarily the project owner.  Has anyone had luck creating a report for this?

We recently came across a warning that we had reach the limit to the number of fields we are tracking in the update feed (300 fields).  Most of these are custom fields.  In many cases, tracking the changes to these fields are critical.  We are a large institution and using Workfront as an Enterprise...