Changes to due date are not reflected in Jira timeline
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
Changes to the Due date field are not reflected on the basic roadmap timeline in Jira.
Check for duplicated "due date" custom field
Jira's roadmap timeline only supports values in system default fields.
If you happen to be using a custom field with the name "Due date," any changes made to this custom field will not get reflected onto the Roadmaps of Jira.
Verify if there is an additional field called "Due Date":
Navigate to
Settings > Issues
Under FIELDS, select Custom fields
- Search for Due Date and see if more than one field is returned
- Note that the system field will not be shown in the Custom fields section
- If so, rename any duplicates to distinguish them elsewhere in Jira
Now that any duplicates have been renamed, check the issue screens in any affected projects to see if those fields are present.
- Navigate to your affected project and select Project Settings
- Select Issues > Screens
- Select the relevant screen scheme and edit any of the relevant screens
- Replace the duplicated fields with the system default Due Date field