DIsplaying multiple publish dates in a report

Right now you're grouping by one field: publication date. Grouping by multiple fields (i.e. can we group by Publication Date, as well as Publication Date 2, 3, 4, ad infinitum?) isn't possible. I suggest you think of ways to make these the same field. This could be as simple as creating a second project to house the second publication date (and so on). Or it could involve housing the publication date on a task and creating multiple tasks in the same project--going this route will probably involve changing your report to look at and group by the task data. -skye

I agree with Skye's assessment on this, and for us that last approach works well, and has a ton of advantages: " housing the publication date on a task and creating multiple tasks in the same project" We initiate through a request queue with custom date fields similar to yours. But when we convert to project we include a unique task for each of those publish dates (one task or several tasks). Each of those publish date tasks makes use of a single custom drop down field for metadata ( "1st Publish Date" , "2nd Publish Date" , "3rd Publish Date" , etc). Easy to run a variety of task reports based on any task with that custom metadata field. Also possible to build calendars using those task dates. The Project Manager can see the publish dates inline in their task list to assess if work is happening at the correct times. Justin White Quality Bicycle Products

Hi William, I just read Skye and Justin's sage advice to your interesting question, and heartily agree that leveraging the 1:many relationship of Project to Task to generate distinct, reportable dates is an excellent approach, which also: allows a different assignment, duration, priority, amount of work, etc. for each such unique Task exposes the powerful concept of setting predecessors (e.g. start to finish, start to start, etc) with or without lags (e.g. +7d, etc) for dynamic scheduling exposes the equally powerful concept of task constraints (e.g. ASAP, Must Start On, Finish No Later Than, etc) for static scheduling fits neatly (and best) into the native Resource and Capacity management features can be efficiently added to a Project using a "mini" template (e.g. a "10-pack" of Release Tasks) should trouble or concern arise for any such unique Task, then supports the native Issue(s) creation that can be tracked and dealt with separately Regards, Doug P.S. In my opinion, Workfront Tasks are normally best used for (planned) work items whose (known) duration will impact a Project's completion, and Workfront Issues are best for (unplanned) work items whose (unknown or immaterial) duration does not. So, wondering if you might consider these release work items "routine enough" that they might seem more natural as an Issue rather than a Task, I had brief debate with myself about that possibility (or, briefly but similarly, as 1:many Expenses, or Documents ,or Notes). But after a brief struggle, in short: I lost. Using Tasks is the best approach. Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads

Thanks Skye, that's very helpful. I went ahead and took your suggestion - created multiple tasks in the same project. However, I still can't get the report to display a separate line item for each send. Do you know of a way that I could report on task level dates in our project level report? William Harnett Federal National Mortgage Association (Fannie Mae)

I can give it a shot. Generically speaking, you have 2 options: 1) Reference the task collection in your project report: https://experience.workfront.com/s/article/Referencing-Collections-in-a-Report-779518987 2) Report on the tasks using a task report and then group by project. Both of these have their pros and cons. I noticed you want to stay with a project level report so it would seem like you have already made up your mind to go the more difficult route. Depending on how you've set up the multiple tasks, you'll be able to set up your report according to the unique features of those send tasks. Going with a task report would be a better option frankly -- and I say this without knowing anything about your situation. The reason being that this will allow you to more easily show on a weekly basis which send tasks are due. It's relatively simple to also display project information for each send task, so you're not losing out on anything there. Either way though, take your pick and have fun experimenting. -skye

Thank you Skye, that's very helpful - I'll give it a shot Sincerely, Bill William Harnett Federal National Mortgage Association (Fannie Mae)

I'm not sure if this helps you or not but these are the things I use to do what I think you are trying to do. When you say "a separate line item" I assume you mean as additional rows, but the only way I know of to do that is a task report. However either a matrix report or a project report can be made to show those publish dates in columns if that works for you. Method one: A task report, filtered to only show any active task that is a publish date task, grouped by plannedStartDate (set to week), with a column showing project name, a column showing which publish date this task represents (usually task name or some metadata), and a column showing plannedStartDate. Notes: this method works the best for us most often, as it offers the good flexibility and the text mode isn't about constantly running collections. Method two (really it's more like one point five): Run a task report as a matrix, with project names along the left, publish dates across the top, and each matrix cell in the middle shows the plannedStartDate for the corresponding email. Notes: these are kind of a pain to setup sometimes, depending on your data, but it can sometimes be a nice way to scan a full agenda, and each publish date for a campaign/journey is nicely in a row. Method three: A project report sorted by whatever seems useful (usually campaign or budget for us), with a column for each publish date (blank if none) Notes: Similar to a matrix but requires text mode and can get complicated. Can offer more customization & information than a matrix. You can't group rows by email publish dates here because there is only one row result per project. Here is some project report text mode to make a column for a single publish date (below). It assumes that you will always use the same task name for your first publish date tasks across all projects. displayname=Publish Date 1 listdelimiter=‍ listmethod=nested(tasks).lists textmode=true type=iterate valueexpression=IF({name}="Your Publish Date 1 Task Name",{plannedStartDate},"") valueformat=HTML Justin White Quality Bicycle Products