Option to Link Planned Completion Date of Issue to Planned Completion Date of Resolving Object

Agreed.

This is still desperately needed. 

This is still causing frustration nearly 8 years later. The planned completion dates should 100% be kept in sync between a resolving and resolvable object!

I'm surprised to find this issue was first reported back in 2017. This does "appear" to be an easy defect to mitigate with an admin setting that can be toggled. We get tons of complaints about the overdue notifications and people not understanding WHY these appear. Our PM's wear multiple hats so any time savers for them are crucial, hoping this makes it onto the roadmap in the near future.

Or at least if there are suggested workarounds, can those be shared for those who came before, or behind me to this thread?

Thanks!

This seems like a basic functionality that should exist. If a request is tied to a project, the request planned completion date should tie automatically to the planned completion date of the project. Currently we have to instruct our teams to remember to manually update the Request planned completion date. Updating the planned completion date of the request is necessary, otherwise folks continue to get overdue notifications on the request if they don't update the date manually.

This seems like a basic functionality that should exist. If a request is tied to a project, the request planned completion date should tie automatically to the planned completion date of the project. Currently we have to instruct our teams to remember to manually update the Request planned completion date. Updating the planned completion date of the request is necessary, otherwise folks continue to get overdue notifications on the request if they don't update the date manually.

Thank you for submitting this request and up voting for it. We won't be able to add this functionality during upcoming 12 months so I am going to mark this as Not Planned for now, but feel free to up vote since we might revisit this decision.

Best regards,

Anna

I created a Calculated Field to show me the "true" Planned Completion Date. It looks to see if the issue is resolved by a project/task/other issue, and then populates it with the resolving object's [Planned Completion Date]. It's got limited use, but it could probably be used in a report?

I made this for Issue custom forms, but I think it'd work for the other object types too.

IF(isblank(Resolving Object Type),Planned Completion Date,if(Resolving Object Type = "PROJ",Resolve Project.Planned Completion Date,if(Resolving Object Type = "OPTASK",Resolve Issue.Planned Completion Date,Resolve Task.Planned Completion Date)))

Note: When attaching this to your issues, you'll want to select the issues you want to update, then Edit > Recalculate Custom Expressions.

Yes, this is needed

I agree this was expected and seems like a design flaw. The option I was given below

"If you were to deselect the checkbox for "keep the original request and tie its resolution to this project" when converting a request, the request will be moved to the recycle bin and all information will be kept at the project level. However, if clients are needing to view the original request and will not have access to the project, you will want to keep that checkbox selected. " would not work for us since clients would lose lists of their requests.

This request started in March 2017. I am fairly new to Workfront and to this voting on issues which is great! Do we get notifications when these are accepted or declined and what release they would be in?