Interactions between the Commit Date and the Planned Completion Date

Both the Planned Completion and the Commit Dates indicate when the task should be completed. But they differ because of who sets each date.

Overview of the Commit Date and Planned Completion Date

Planned Completion and Commit Dates exist on both tasks and issues.

The following table contains information about the difference between the Commit and Planned Completion dates:

Interactions between the Commit Date and the Planned Completion Date

When the project owner creates and assigns a task or an issue, the task or issue will have the following:

The assignee working on the task or issue can manually update the Commit Date or automatically update it by accepting to work on it. This is a visual way to indicate to the project owner when it would be realistic for them to complete the task or the issue.

The assignee changing the Commit Date does not automatically change the Planned Completion Date. The reverse is also true: changing the Planned Completion Date will not change the Commit Date.

When the Commit Date changes to a date later than the Planned Completion Date, the Project Owner gets notified that this change occurred and it could impact the timeline of the project, if the Project Owner uses the legacy commenting experience. This functionality is not supported in the new commenting experience. For more information, see New commenting experience.

If the Commit Date offered by the assignee is acceptable to the project owner, they must manually update the Planned Completion Date on the task or issue. For more information, see the following articles: