ah, that's a tough one since Workfront calendars do not currently operate off custom fields. You're specifically looking to tie it into the planned completion date of a project, task or issue. It's fair and not unusual for most project planned completion dates to go past the launch date, but that means you're looking to tie it into a task or an issue planned completion date instead. Is this something you can get your users to adopt? I've had pretty good luck on both fronts: my teams have either agreed to use a task as a launch date or an issue. The issue one has been particularly nice, since I've set it up as a request queue in the project so that when they select "Create calendar entry" it gives them everything they need to set it up: planned start and completion dates (our events operate on duration, not one single date) and locations to pick from. The other thing the issue option helped is: it gave the Project owner the ability to state multiple entries (multiple events per project), and it keeps those entries out of the way of the actual project task timeline, so there's no clutter. On the other hand, I have had events teams who specifically want their launch date IN their project timeline so they can set predecessors around this date: and that's fine as well! It's all about what your teams are willing to do and how the options benefit them. -skye
