What functionality (if any) is associated with "Start Date" and "Target Date" fields in Features and Epics for Azure DevOps?

Question

I'm using Azure DevOps with "Scrum" Process templates. I would like to know if "Start Date" and "Target Date" fields in Features and Epics are purely informational, or is there specific functionality associated with them?

If there is a functional aspect to these 2 fields, please explain where and how the fields are used in Azure DevOps. As an example, Iteration start and end dates are used to render the Feature Timeline of the Backlog Board, but I don't see any effect of a Feature's "Start Date" and "Target Date" fields on the Feature Timeline.

Answer 1

They are just the common fields for Epic and Feature work items. The Epic and Feature have different backlog levels with other work item types as defined in Scrum process, and they will also render the project timeline.

Start Date : The date and time when the schedule indicates that the epic/feature will start.

Target Date : The date by which a epic/feature should be completed.

Se we can Select backlog navigation levels for your team. Each team can determine the backlog levels that they use. For example, feature teams may want to only focus on their product backlog, while a management team may choose to only show feature and epics (the two default portfolio backlogs). You configure which backlog levels appear from your team settings dialog.

Generally we can simply know when Epics/Features must be started and delivered via a Start Date and Target Date to ensure they do not fall out of an iteration.

We can also query the specific Epics or Features by the fieldes. Please see Query by date or current iteration for details.

Answer 2

'Delivery Plan' provides a timeline view for project based on selected teams and backlog level. Delivery Plan uses start date and target date of work item types to generate this timeline. Drag of items card edges in Delivery Plan enables updating the dates. It's a handy features