Does logging time towards a project, versus time towards a project's task affect resource budgeting or project costs? At one point, our team was directed to create a general PM task that spanned the duration of the project for tracking general PM activity. The purpose was to avoid entering time at the project level. I'm struggling to understand why that would be necessary.
Topics help categorize Community content and increase your ability to discover relevant content.
Having PM's log time at the Project level for simplicity is a fairly common practice (so much so that we made it an optional setting in our Enterprise Stopwatch solution), and yes, those hours (and costs, if you've set them up) to then "count" against the Project's actuals. You must first choose to allow time to be tracked at the Project level as a global setting within Workfront (noting that it might be "off" in your environment, by default). On the flip side of the coin, some customers prefer to only allow time to be entered at the Task level on everything (even a single project-long "PM Time" Task), preferring to have hours specified at the lowest common denominator, and noting that they still then do roll up to the Project level total actual hours and costs.