@Jay_Miller
thank you for your explanation.
I made a dependency like below,
In my environment, when I move ‘anticipated install date’ task in timeline view, specific due date also change.
In my environment, when I move ‘anticipated install date’ task in timeline view, specific due date also change.
Tetsuo,
Yes, agreed, that is what we have setup to manage that part (Dependencies). It is getting that ‘To Engineering’ date on the portfolio screen, and to update daily properly. As you see in my last post, as the days progress, but no one physically changes ‘Handoff to Engineering date’ the DueDate-Today2 does not stay in step with the ‘DueDate-Today’ count. It just remains fixed based on when the rule last ran.
It is like the rule needs run daily to evaluate the due date - today value daily and update that to the Portfolio view, otherwise the dates in the project level and the portfolio level get out of step with one another as I tried to show in the screen captures.
Perhaps there is another way entirely to accomplish this?
Thank you!
@Jay_Miller
Finally I recognized my misunderstanding. You use the old version!
The old version doesn’t work well. So I offered the new one below,
Could you tell me why you use the old?
Honestly, because I thought it was working up until very recently and it would be a simple adjustment to ‘fix’ this one. I struggle to set these things up and don’t want to break anything else we have going on in there.
So I am clear on the ‘new’ one. Remove all elements of the ‘original’ version of this, and then do the ‘new’ one? Or do ‘both’ need to be active for things to work?
Thank you,
A couple weeks ago I wanted to share your great solution with a client, and did, but frankly I got lost in following it. The post you marked as the solution says “this post is wrong” and then gives other instructions.
Would it be possible to modify the original post so that it’s correct and that one post can be followed solely, in order, to implement, and reduce confusion?
Thanks,
Larry
@Jay_Miller
I modified the original post.you can try the newest ver.
It is simpler than old ver.You just do only the newest one.
This doesn’t use today() function. Due to that, nothing is changed daily.
I hope you can achieve what you want to do.
1 Like
Thanks so much, @Tetsuo_Kawakami, for making this perfect now!!
Larry
1 Like
Tetsuo,
Thank you so much for working through this! It is a huge help, and seems to work very well!!! I like it is not using a ‘rule’ to trigger, it just’ exists and updates as things ‘go’. THANK YOU!
Now that this is running in our ‘main’ portfolio, there is some refinement that I see could be advantageous, if possible. Much like the ‘Due Dates’ that Asana generates turn RED if the date is past the current date. Is there a way to do this here? Some kind of conditional formatting or similar that if a date gets reported in the “specific due date” field, that is before ‘Today’ can it have a red font? Perhaps this topic is addressed elsewhere on the forum?
Even more refined refinement question: Is there a way to make a date populate automatically in the ‘dummy date’ field of the Project and Portfolios that have the ‘dummy date’ field? Since the date does not matter, other than being the same. We plan to play around with some rules that trigger at creation to hopefully fill this in, but we may skip it if a lot of work, and just let the project owner do this as part of project launch, it is not very burdensome. If you have any thoughts on a simple way for these to fill in consistently, that would be a bonus.
Thank you again for a tremendous solution!
Just following up, @Tetsuo_Kawakami, that this worked well for my client and me; thanks!
For others:
- I was confused about the use of the 1. “specific-task” custom field. It’s actually completely optional and in no way needed to achieve the linking effect. Users may already be using their own manner of designating the task with the due date in it to promote to the portfolio, or not need to identify it this way.
- Instead of the 2. “dummy date” field name, I used: “Arbitrary Date Received | Match in Project&Portfolio” (replace “Received” with what your date is for).
- Instead of 5. “due date - dummy date” field name, I used “fx Calc Date Received | Project&Portfolio”. I hid this from Portfolio and Project column views since it’s just for internal use.
- Instead of 7. “specific due date” I used “Date Received”.
All of that helped us keep track of things more easily.
Thanks,
Larry
1 Like
This is a brilliant workaround!! 
@Tetsuo_Kawakami
2 Likes
What previously worked for me is currently no longer working for me. I describe it all here:
Have you tried this whole approach in the last day or two? Is it working for you? Did you find some approach to make it work after it failing? My client and I are stuck; it worked before but not now and we wonder if it’s related to the bug linked above, and if you have any known workaround. Note that a couple things we tried didn’t help.
Thanks,
Larry
@lpb
I confirmed that now.
In my phenix environment ,it work well.
I’m not sure that why it work well…
1 Like
Ah, I just reported the same here!
Seems like it is affecting Asana spaces on legacy plans, not new/existing plans.
1 Like
It says bugs are fixed now.
Therefore, Step6 isn’t required any more now.
In my environment, I could confirm that.
1 Like
I can confirm it’s working again for me after Asana’s deployed bug fix:
1 Like