要約

On a team-managed backlog screen, we can't see the due date field next to any work items. 

The Due Date field was already added to the issue layout.

Confirm the field is added to the Context instead of the Description 

If the field was added to the Description section of the layout, the field will not appear in the backlog. According to Jira's interface:

Description fields: These fields describe the work that needs to be done. They display prominently in most views.
Context fields: These fields provide context to the work, and help group, filter, and report on similar issues

Let's verify the due date field is in the right section of the issue layout:

1. Go to Project Settings → Issue Types 
2. Select one of the affected Issue types
3. If you find the field in any part of the layout besides Context, drag and drop the field to the Context part of the layout
   1. In the below image, the field is part of the Description section, and should be moved under Context fields
      
      

Once the change is done, you can enter a value in the due date field and verify it is reflected on the backlog.

If the field is already in the Context section, proceed to the next solution.

Use system Due Date field instead of a custom field

The Due date field added to the project might be a custom field and not the actual Due Date field. 

Jira's backlogs will only display values from the system Due Date field, and can't work with a custom Due Date field.

1. Open an issue where the Due Date is not displayed on the backlog, but the Due Date field has been filled
2. View the issue via the REST API
   1. In your browser address bar, replace /browse/ with /rest/api/3/issue/ 
   2. For example: https://<your_site>.atlassian.net/browse/TEST-1 becomes https://<your_site>.atlassian.net/rest/api/3/issue/TEST-1
3. Search for the duedate field

If you find the actual value of the Due Date next to "duedate," then the correct field is in use. If duedate is set to "null", then a custom field is being used in place of Due Date.

In the below example, customfield_10046 was a custom field used in place of the actual Due Date field. The real Due Date field (shown as "duedate" via the API) does not have any value entered. 

To fix the issue, visit the issue layout editor, and add the actual due date field to the context part of the issue layout.

Once the field is added, you can enter a value on the newly added Due date field and verify if it is reflected on the backlog.

If the Due date is reflected on the backlog, then you can remove the previously used Due date custom field.