It would be great if the new type ahead custom fields also supported
other major record types such as projects, tasks, and issues (in
addition to users). This would grant the ability to effectively create a
clickable link from record to another thus enhancing the user
experience. Also, this would he...
I just spent 3 hours manually migrating hours logged by 11 people over
the course of 1 month from one project to another... I feel braindead.
The reason it took extra-long was because Workfront tracks the hours to
the owner, as such each time a system admin (or a user with the right
Fantastic suggestion! One small issue is that teams are cross-company
and cross-group, meaning that group admins technically have no business
managing teams. I'd like to suggest a small adjustment to this - if the
team owner (creator) is also a member of one of group admin's managed
groups, then tha...
This feature would be extremely useful; currently the fact that the
"Deliver this report with the Access Rights of:" field is required is
crippling our ability to disseminate "personalized" reports (with filter
criteria that includes user wildcards) and no reasonable workarounds are
Vazgen, I'm less concerned about this particular change (since it's
rather small) but more concerned with the general direction of updates
being pushed into production without much notice as of late. In
retrospect, perhaps it would have been more appropriate not to roll out
this feature into product...
Would be super-useful! In general it would be even better if we could
have a filter for an export of each record type (not just projects) so
that it would be easier to make bulk-updates of specific record sets
during an import.
Agreed! WF API doc needs a new look and functionality, my particular
complaint is when an object exists independently of a parent record yet
there's no way to fetch it with an API call... madness 😄 It should be
crystal-clear to any semi-technical admin working with exporting or
importing data via R...
Upvoted! If form isn't completely blank carry it over to the resolving
object. Better yet, custom forms should be made agnostic to a record..
just like custom fields are agnostic to forms. Why have multiple copies
of the same darn form for main objects when you can just have one.