What task field will allow their due dates to be set . I don't want this field prepopulated.

[BenettaPe]

What task field will allow their due dates to be set . I don't want this field prepopulated.

[JasonMa]

I believe all date related fields on a Task auto-generate at Task Creation. When you create the task, it will set the Planned Start Date to one of three values: the date you choose from the picker/manually type, the Start Date fo the project, or a date based on a Predecessor that is entered while creating the task. With a Planned Start Date, the system then creates the Projected Start Date, Planned Completion Date, and Projected Completion Date automatically based on several factors including the duration you enter for the task and the effort+resource availability of the assigneee/group. To my knowledge, it is not possible to leave any of those blank or prevent them from calculating based on the fields/factors above.

[JasonMa]

Having said all that, you could always create a Custom Field with a Date data type on a Custom Form and attach it to a Task and use it how you want. It won't auto fill the field and then you could adjust Views and Reports to use that date, however, it would likely not interact correctly with a lot of other key functions in Workfront, so you would have to do what works best for your scenario.

[BenettaPe]

Thanks Jason. I have to think thru your reply. Our projects are based on Planned Completion Dates. So I might create a custom field in a form - but if I have 50 tasks, can 10 assignees modify this field and it will be modified for only their assigned task?

[JasonMa]

As long as each task is assigned to only a single resource, that would work (if multiple people are assigned to a single task they would be editing the same field). What are you trying to accomplish? Someone else here might have succeeded in doing something similar without the need to create a custom field.

[BenettaPe]

I have a list of tasks. Only 1 person assigned per task. I want to enter their due date or I want them to enter their due date. What preexisting field can we use? Thanks. [image: APS Payroll logo] Benetta Perry New Client Setup Specialist p: 318-222-9774 f: 318-222-0601 e: bperry@apspayroll.com www.apspayroll.com < ">http://www.facebook.com/apspayroll> < ">https://twitter.com/apspayroll> < ">https://plus.google.com/u/1/101565211370298693012/posts> < ">http://www.linkedin.com/company/aps-payroll> The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. On Tue, Nov 8, 2016 at 8:53 AM, Jason Maust < globalforum@communitylists.workfront.com> wrote: > As long as each task is assigned to only a single resource, that would > work (if multiple people are assigned to a single task they would be > editing the same field). > > What are you trying to accomplish? Someone else here might have succeeded > in doing something similar without the need to create a custom field. > > -----End Original Message----- >

[BenettaPe]

I have a list of tasks. Only 1 person assigned per task. I want to enter their due date or I want them to enter their due date. What preexisting field can we use?

[JasonMa]

Is the challenge you are facing that Planned Completion Date automatically generates a value and you want it left totally blank until someone fills something in (as to not create confusion or "missing" entering a date because it's easier to look for a null value)? If you add to the standard Task List view of the Project the Commit Date field and share that field, that seems to be left blank until someone accepts the work and actually changes the Planned Date. This would be easy for someone to go down in a custom view and just enter the Commit Dates. The only challenge is it appears that ONLY the task assignee can enter a Commit Date in that field. The Project Manager/Project Owner would have to continue using Planned Date and that will continue to have a pre-generated date.

[BenettaPe]

Jason, Yes, that is the challenge. Thanks for some options. Let me play around with both fields. Thanks,

[BenettaPe]

This is the solution I used. I created a date field in a custom form. The custom form was attached to the Task object. On every task, in the master template, I attached this custom form. Now I am able to display this date field in the views or in reports. This field is totally editable by all, as it is just a date field we are using for our Due Date.

[DavidCo3]

Hi Benetta, One other option which you might like, is to give the assigned users 'Manage' rights to the task when they are assigned to it (this can be configured to happen by default in the project template settings). They can then change the planned completion date of their task. In addition, you can then use custom formatting to highlight the planned completion date field a colour (e.g. green) if it was last updated by the assigned user. That way you and they can easily see which tasks have been updated by them or not. The text-mode code to do this is below...you can just edit the planned completion date column in text mode and paste everything below on top of it. If you want to change the colour, then you change the trueproptery.0.value= to something else. descriptionkey=plannedcompletiondate isInlineEditable=false linkedname=direct listsort=atDateAsAtDate(plannedCompletionDate) namekey=plannedCompletionDate querysort=plannedCompletionDate section=0 shortview=false stretch=0 styledef.case.0.comparison.icon=false styledef.case.0.comparison.leftmethod=lastUpdatedByID styledef.case.0.comparison.lefttext=lastUpdatedByID styledef.case.0.comparison.operator=eq styledef.case.0.comparison.operatortype=text styledef.case.0.comparison.rightmethod=assignedToID styledef.case.0.comparison.righttext=FIELD:assignedToID styledef.case.0.comparison.trueproperty.0.name=bgcolor styledef.case.0.comparison.trueproperty.0.value=def6e2 styledef.case.0.comparison.truetext= textmode=true valuefield=plannedCompletionDate valueformat=longAtDate width=150 Regards, David