Hi - we have tried various things... Using "task name contains": Not recommended. No matter what we try to do, people have a hard time sticking to naming conventions. Using Template Task ID: This worked well for some accounts (not for a whole business unit or even instance wide) You can filter by various Template Task IDs so you can include all the "send" tasks across all your templates for that report or calendar Using a custom form on the task to tag it: This has worked out the best for us. What we did is create a Standard with Tagging view so as they are making changes to the template after it is attached or if they are starting from scratch, they can easily just click in that column and tag it. We can then build various reports and calendars with it. Using Milestone Paths on a project: Now that they have milestone diamonds on the Gantt chart, we do have a few accounts using the milestone paths to tag tasks. Some thing to thing about though:
You can only use a milestone once. So if you want to track things like Client Meetings, you do need to have Client Meeting #1 Client Meeting #2, etc.
When building reports, a Milestone ID or Name is specific to one project (i.e. Client Meeting #1 on Project ABC has a different ID than Client Meeting #1 on Project XYZ). So for your report or calendar, you will need to do a filter that is 'Milestone name contains Client Meeting".
If it is like a hot sheet were you are showing all milestones due in the next 3 days and you want to use the grouping, you have to play around with the text mode to get the naming down. (Let me know if you are interested in this and I'll send you the code I've used and how you can manipulate it.
Hope this was helpful. Anthony Imgrund FCB
