Hi @DanaLa3,
I think I wrangle my new Echo technique to detect and highlight Parent Tasks whose Children (and Grandchildren, and Great Grandchildren, etc.) are all Not Applicable so that you could then (manually) also mark such Parent Tasks as Not Applicable, with confidence.
If that sounds ap...
Thanks for spitballing with me@Kasey-Gagne,
In the context of our AFA Burn List solution, AFA stands for Approved/Forecast/Actuals conceptually, which equate to Baseline/Planned/Actuals within Workfront specifically, and rolls "up" to the Program, Portfolio, and Standalone level (across multi-cu...
Hi @Kasey-Gagne,
Although it might be more than you need, I invite you to consider our AFA Burn List solution which tracks Rates, Hours and Hour Costs at the Total, Portfolio, Program, and Project level.
In particular, the far-right section of this screenshot shows the Remaining Approved Hours...
Hi @Greta_12-25,
I've cued up this video to highlight a native-Workfront technique @ScottMo1 and I developed (as part of our Lite-Brite solution) that I believe you could use to accomplish your "Lock or Freeze Allocations" requirement...particularly if you also consider using it in conjunction w...
Hi @JHulet,
If, in addition to seeing just the Children Tasks that Can Start, you'd also like to see all Tasks (including grandchildren, great-grandchildren, siblings, cousins, etc.), I invite you to consider this thread.
Regards,
Doug
Hi @RJHulett,
As I mentioned on your Next Subtask Column in Task Report post, I invite you to consider adding the project. prefix to your original attempt, to go "up, then down" in order to Echo all of the Tasks of interest to all other Tasks.
description=Tasks Ready to Start
displayname=Next ...
I'll be your huckleberry, @NCorver.
For your Restaurant example, and staying within Native Workfront capabilities, I propose:
Each meal (3 course dinner, in your example) is a Template with one Template Task for each phase (e.g. Starter, Main, Drink)Each menu item is an independent Sub Templat...
Hi @TimBaker,
Following your example, and imagining custom parameter X on both Custom Forms A and Custom Form B, if custom Form B is deleted, all X-entered data that was ONLY on Custom Form B will be deleted, and all X-entered data that was ALSO or ONLY on Custom Form A will be preserved, untouc...