Bring back commit dates to the updates tab! | Community
Skip to main content
April 11, 2024
Delivered

Bring back commit dates to the updates tab!

  • April 11, 2024
  • 13 replies
  • 2696 views

Description -

Our team relies on commit dates to plan out and communicate our workload every morning to our lead. This helps us know if we are able to take on more work or if we need to push out work. Having easy access to it is very efficient. The process we had in the updates tab was a simple dropdown 1 step process that was separate from the completion date which made it easy to identify it and update it. 

13 replies

April 11, 2024

Yes please! 🙌

April 11, 2024

Yes please! it was more convenient before. Thank you!

lid12
April 11, 2024

with commit dates in the updates it was more organized. Absolutely agree on returning this feature back!

MarkTEvans
April 16, 2024

Please Sir, may I have this back!!

April 16, 2024

+1   Also updating planned dates based on commit dates from the prompt in system updates.

BGibas84
April 19, 2024

That would be great!  This is a hot topic of discussion in our organization.

Susan_Hart_DeltaDental
April 23, 2024

YES! 

I submitted a video to Workfront showing that users now have to click into task details to commit to a new date via the 'commit date' field INSTEAD of being able to do this by adding a new comment. In addition, even if a user does this and commits to a new date, the ability for a project owner to accept the new date no longer exists. I am so bummed by Workfront's response below and am shocked they didn't account for this before rolling out new commenting, especially because I gave this feedback multiple times that committing to a new date is critical.

WORKFRONT STATED THE FOLLOWING

After investigation, Our development team does recognize that there is indeed an issue here that they need to review in more detail. However, because of the time and effort it will take to build out the improvement, the work for this fix has been converted into a story, which is not something we can keep a support case open for. Stories are work items that are added to the team’s backlog and worked on over a period of time. There are no ETAs given on story work due to this.

I have given the following direction to our team as a workaround: If a team member needs to commit to a new date/an extension, they should tag the project manager in an update on that task stating the new due date they would like, then the PM needs to change the planned completion date of that task.

Anna_Asatryan
Adobe Employee
Adobe Employee
November 8, 2024

Hi All,

 

Thank you for submitting the feedback.

 

With the June release we have introduced the ability to add commit date and condition fields to the header area of tasks and issues. I understand this is not added in the commenting area, but users can still see the field front and center and easily update the information without going to the details page. Here is the help article describing this in more details. 

 

Let me know if there are any additional questions/comments.

Anna_Asatryan
Adobe Employee
Adobe Employee
November 8, 2024
No text available
Susan_Hart_DeltaDental
November 8, 2024

The ability to commit to a new date must exist as a column in the My Tasks widget OR as a field in the summary that appears after clicking the summary icon from the My Tasks widget. Clicking to open the entire task to commit to a new date isn't efficient.