From EOY Reporting Workshop - Continued discussion on Actual vs Planned with keeping tasks late vs updating late tasks | Community
Skip to main content
Level 2
December 15, 2022

From EOY Reporting Workshop - Continued discussion on Actual vs Planned with keeping tasks late vs updating late tasks

  • December 15, 2022
  • 5 replies
  • 4021 views

Creating this for us to talk about the discussion that started in the EOY Reporting Workshop about the idea of updating tasks to be not late and how that applies to reports

@justin_charles and I can't find Madalyn yet

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

5 replies

Madalyn_Destafney
Community Advisor
Community Advisor
December 15, 2022

Hi @andreadmw & @justin_charles here I am : ) 
I will share the report info for what I was chatting about today (project Current to Complete) here by EOD, may be tomorrow morning (lots of meetings today!). Would like to learn more about what you're doing too, Justin.

If this helped you, please mark correct to help others : )
andreadmwAuthor
Level 2
December 15, 2022

REALLY appreciate it. I'd love to play around with with you and Justin were talking about and see how I can utilize this

Level 3
December 15, 2022

hi there!  happy to help - let me know if you have any questions i can answer.  i can also get on a quick call to share my screen to show you how we have things set up if you'd like.

NicholeVargas
Adobe Employee
Adobe Employee
December 15, 2022

Thank you Andrea for allow everyone to continue the conversation! I wanted to share the text mode that came up after the workshop was over around calculating the number of days between Proof Creation and Proof Decision date (on a Proof Approval report).

 

displayname=# of Days Between Creation and Decision 
textmode=true 
valueexpression=WEEKDAYDIFF({proofCreationDate},{decisionDate}) 
valueformat=HTML 

Madalyn_Destafney
Community Advisor
Community Advisor
December 16, 2022

Sweet I'm going to try this out, this will help me have real proof - see what I did there? ; ) - about ppl taking too long to review proofs!

If this helped you, please mark correct to help others : )
Madalyn_Destafney
Community Advisor
Community Advisor
December 16, 2022

Hi all, sharing a few text mode snippets for things I mentioned on this week's workshop:

 

Tracking Project Creation/Entry to Completion Status – you’d create a calculated field for this on any necessary project forms:

ROUND(DATEDIFF({actualCompletionDate}, {entryDate}),1)

 

Tracking Project turning Current to Completion Status – separate field on any necessary project forms. I like this better than above bc for us, when it turns Current is really more day 1 of work starting, but I still like to know for reference entry to completion to see if projects were sitting before turning Current and then rushed timeframe:

IF(ISBLANK({DE:Project Current to Completion}),IF({status}="CPL",ROUND(DATEDIFF({DE:Date Went Current},{actualCompletionDate}),2)))

 

As you can see, this field requires you to first make a ‘Date went Current’ field in the same custom form, here’s the text mode for that:

IF(ISBLANK({DE:Date Went Current}),IF({status}="CUR",$$NOW),{DE:Date Went Current})

 

From here, you can pull various project reports to show these timings with charts. For us, we like to know by project type. We have a field for project type on each project. So you can get a report like this to see QoQ or MoM generally how long any project type(s) are taking from time they go Current to when Complete (we don’t use from time of creation or Actual Duration bc there is often planning-related things while it’s in Planning and hasn’t really started yet). Tricky part is the project type is a multi-select field, which can be a pain for grouping (whole other topic).

If this helped you, please mark correct to help others : )
andreadmwAuthor
Level 2
December 16, 2022

Thank you!!

Madalyn_Destafney
Community Advisor
Community Advisor
January 4, 2023

Hi all, wanted to share another reporting idea that I created last week in case anyone else would find this helpful!

 

I was curious to know how many rounds/versions our Proofs are going. This 'document version' report shows Proofs by # of versions that were uploaded over the past rolling 6 months. This can show trends on average number of rounds on Proofs (i.e. if most Proofs are going more than 2 rounds, there is a bigger problem to dig into).  NOTE: this is only a credible report if your teams are good about Proof versioning (we aren't perfect but getting there). The report will end up looking like this so you can keep an eye on versions and dig into the few that are high:

My filters (I say proof name not blank bc I only want proofs, not document approvals or other documents) and only have those teams that upload proofs:

Text mode for your grouping:
group.0.groupdatesby=MY
group.0.linkedname=direct
group.0.name=Upload
group.0.notime=false
group.0.valuefield=entryDate
group.0.valueformat=atDateAsMonthString
group.1.iscollapsed=true
group.1.linkedname=direct
group.1.name=Versions/Rounds
group.1.valuefield=version
group.1.valueformat=string
textmode=true

And this for your chart:

 




 

 

If this helped you, please mark correct to help others : )
Level 2
January 11, 2023

Thank you for this!  I'm curious about trying to capture the number of comments on a proof.  Have you tried this? 

Madalyn_Destafney
Community Advisor
Community Advisor
January 11, 2023

Hi there, I have not tried that, but not sure if that is possible. This is a document version report and it definitely doesn't pull that in, but I tried a document report just now and not seeing a way there either.

I'd ask though, even if you were able to pull in # of comments on a proof, that wouldn't necessarily correlate with # of changes or even the scope of the comments since some comments may be along the lines of 'looks great!' or some may be questions from the proof owner to clarify proof comments, etc. Pulling # of comments could be misleading in whatever you're trying to glean from that.

If this helped you, please mark correct to help others : )