Report on changes to the planned completion of milestone tasks.

[RichardHu2]

With the new Journey entry report capability, it is possible to report when the planned completion date of a task changes. This is useful but the journal report only reports on changes to the tasks I have edited myself, NOT any later tasks impacted by this change and linked using predecessors.

I'm particularly interested in running a monthly report showing changes to planned completion dates of any milestone tasks across a range of projects.

If anyone can assist would be much appreciated

Thanks

[TealeMcCleaf]

Hi Richard,

Instead of a journal entry report I might suggest using a baseline variance report. We have the system set to automatically create a baseline when the project status is put into Execution. I then created views and reports that show the variance in planned, projected and actual dates for the tasks. You could filter it so that it only shows tasks with a milestone ID.

Here's what I use in a task report for the variance:

Baseline PCD vs PCD

descriptionkey=plannedcompletiondate

displayname=Baseline PCD vs Planned Completion Variance

linkedname=direct

listsort=atDateAsAtDate(plannedCompletionDate)

namekey=plannedcompletiondate.abbr

querysort=plannedCompletionDate

shortview=false

stretch=0

styledef.case.0.comparison.attribute=css

styledef.case.0.comparison.isrowcase=false

styledef.case.0.comparison.leftmethod=atDateAsAtDate(plannedCompletionDate)

styledef.case.0.comparison.lefttext=plannedCompletionDate

styledef.case.0.comparison.operator=notnull

styledef.case.0.comparison.operatortype=date

styledef.case.0.comparison.righttext=

styledef.case.0.comparison.trueproperty.0.name=bgcolor

styledef.case.0.comparison.trueproperty.0.value=ffffff

styledef.case.0.comparison.truetext=

styledef.case.0.comparison.usefield=false

textmode=true

valueexpression=ROUND(DATEDIFF({defaultBaselineTask}.{plannedCompletionDate},{plannedCompletionDate}))

valueformat=HTML

width=75

Baseline ACD vs ACD

descriptionkey=actualcompletiondate

displayname=Baseline ACD vs Actual Completion Variance

linkedname=direct

listsort=atDateAsAtDate(actualCompletionDate)

namekey=actualcompletiondate.abbr

querysort=actualCompletionDate

shortview=false

stretch=0

styledef.case.0.comparison.attribute=css

styledef.case.0.comparison.isrowcase=false

styledef.case.0.comparison.leftmethod=atDateAsAtDate(actualCompletionDate)

styledef.case.0.comparison.lefttext=actualCompletionDate

styledef.case.0.comparison.operator=notnull

styledef.case.0.comparison.operatortype=date

styledef.case.0.comparison.righttext=

styledef.case.0.comparison.trueproperty.0.name=bgcolor

styledef.case.0.comparison.trueproperty.0.value=ffffff

styledef.case.0.comparison.truetext=

styledef.case.0.comparison.usefield=false

textmode=true

valueexpression=ROUND(DATEDIFF({defaultBaselineTask}.{actualCompletionDate},{actualCompletionDate}))

valueformat=HTML

width=75

ACD vs PCD

descriptionkey=plannedcompletiondate

displayname=Actual vs Planned Completion Variance

linkedname=direct

listsort=atDateAsAtDate(plannedCompletionDate)

namekey=plannedcompletiondate.abbr

querysort=plannedCompletionDate

shortview=false

stretch=0

styledef.case.0.comparison.attribute=css

styledef.case.0.comparison.isrowcase=false

styledef.case.0.comparison.leftmethod=atDateAsAtDate(plannedCompletionDate)

styledef.case.0.comparison.lefttext=plannedCompletionDate

styledef.case.0.comparison.operator=notnull

styledef.case.0.comparison.operatortype=date

styledef.case.0.comparison.righttext=

styledef.case.0.comparison.trueproperty.0.name=bgcolor

styledef.case.0.comparison.trueproperty.0.value=E1E1E1

styledef.case.0.comparison.truetext=

styledef.case.0.comparison.usefield=false

textmode=true

valueexpression=ROUND(DATEDIFF({actualCompletionDate},{plannedCompletionDate}))

valueformat=HTML

width=75

I'm not very familiar with the journal entry report yet but hope this helps as a workaround.

Best -

Teale

[RichardHu2]

Hi Teale, thanks for your response that's a really useful thought.

I think this approach relys on people resetting their baseline though, I may be wrong please correct me if I've misunderstood. Unfortunately, I can't necessarily rely on users setting a new baseline when they update their plan dates.

Richard

[TealeMcCleaf]

Hi Richard,

Yes, you're correct, that is the challenge. I've suggested to users that want this info to snap a baseline when phases of their projects complete.

It would be nice to have some functionality that shows how changes affect the subsequent tasks in the schedule, like MS Project, but we're not there yet.

Good luck,

Teale

[Doug_Den_Hoed__AtAppStore]

Hi Richard,

I concur with Teale, and invite you to consider our Create Baselines solution, which can automatically create a baseline for multiple Workfront projects on a scheduled basis, providing you a wealth of reporting information to leverage for trends and insight (such as this one).

Regards,

Doug