Logging time: how granular are tasks in your project timelines? I'm running into an issue where designers are struggling to log their time because our tasks are too granular. For example, we include each revision round in our timelines so it shows Round 1 (parent task) > Design, Copy Writing, Stakeholder Review (children tasks). When there are many rounds, it shows up in designers' timesheets as Project Name > Design, Design, Design -- because it shows tasks from multiple rounds, but the parent tasks aren't listed, so they don't easily know where to log their time.
Another issue is how to log meeting time. Inputting a meeting task every time there is a meeting, and then making sure you log time to the correct meeting, is too time consuming.
The feedback I'm getting is it would be much more simple to have general buckets to log time against for each project such as Research, Design, Meetings/Reviews, etc. The only way I know how to do that is to have tasks with these names that run the entire l
