I'd just add a suggestion to upvote this idea as well -- we really
should be able (as named Sysadmins) to change the owner of a Calendar
without having to resort to these workarounds!
The way this works is kind of, if you'll pardon the expression,
crazy-making. I've read the suggested workarounds to have a generic
sysadmin account to be the owner of calendars and then have multiple
actual admins use that account to do certain things, but that is
terrible from a governance and auditability perspective, not to mention
actual security. And having to use up an additional paid account adds
injury to insult for sure!When someone who actually owns a calendar in
real life leaves, Wor...
Hi Matt, this may expand on the topic somewhat, but our biggest issue
isn't that the number of rows of detail is limited in the initial view
(talking especially about a report in a dashboard), its that whatever
you have built into the grouping header for the report (which is often
the reason you built the report in the first place) -- be it an average,
or a sum, or whatever it might be -- only takes into account the visible
rows, not all the data for the report.We have to explain and remind our
To Malcom's comment, there is a related idea that captures the
multi-select request for typeahead fields:
indicated as on the Roadmap (yay!) with a request for more use cases, in
case that's helpful!
@Jason Webre‚ I'm working on a document report and trying to have the
report and groups sort by Sponsor Name. It's technically only 2 jumps,
but because of the way we have to modify the syntax to have a column be
Sponsor Name (vs. ID), does the system count that as 3 jumps, and
therefore the group sort by Sponsor Name won't work?
querysort=project:sponsor:name I'm hoping there's some other thing I'm
missing (oh how I wish Sponsor Name was just there :-)), but thought I
We just expanded WF use to another team within our company (for email
marketing projects) and this came up as a big issue and something they
had in Basecamp (which we asked them to move off of to adopt Workfront
instead.) I also notice at least 2 other Ideas asking for this same
thing, perhaps they could be consolidated into this
Further, it seems you can only add/edit the Proof Description *after*
you have created a proof, by selecting 'Document Details' from the proof
section in the Project Documents tab. Why not include the Description
field in the form when you create the proof? Thanks!
While creating reports for our management-level sponsors to see hours
spent across groups & teams for the projects they sponsor, we were
surprised to find that unless they have Manage permissions on the
project, Sponsors can only see Hours for their own teams (either within
the Project navigation or on reports.) We then found there is no way to
set up the project template or other permissions to grant Manage
permissions to whoever the Project Sponsor is (in a dynamic way so we're
not attempting ...
@Cortney Devine‚ you might also take a look at this Idea and if it
strikes a chord, upvote it as well! It's written from the perspective of
the importance to collaborators, but in our internal discussions our
project managers have also voiced that they'd like a central place to
see (and interact with, which you can't do from a report or dashboard)
all updates. I believe it used to exist for collaborators but not PMs,
but really is needed for both, IMHO!