要約

The due date field needs to be visible on issues in the Team Managed project backlog.

環境

Jira Cloud Team managed projects. 

診断

On the backlog screen, we can't see the due date field next to the issues even though the Due Date field is added in the issue layout. 

原因

Probable cause 1: The Due date field is in the Description part of the screen and not the Context part. 

Probable cause 2: The Due date field added to the project might be a custom field and not the actual due date field

ソリューション

Solution for cause 1:

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

Please follow the below steps to verify if the due date field is in the right section of the issue layout:

1. Go to Project Settings → Issues Types. 
2. Select the Issue type you want to verify. 
3. Verify if the Due Date field is added in the Context part of the screen. If you find the field in any other part of the layout, such as Description, drag and drop the field to the Context part of the layout. In the below image, the field is under the Description field. This should be moved under Context fields for the Due Date field to function as expected.
   
   
4. Once the change is done, you can enter a value in the due date field and verify it should be reflected on the backlog.

Solution for cause 2:

1. Open an issue where the Due Date is not displayed on the backlog, but the Due Date field has been filled. 
2. Try viewing the issue in API mode so that all the fields used in the issue will be listed. You can do this by replacing /browse/ from the issue URL to /rest/api/3/issue/. 
3. If the issue you are viewing has the URL: https://test123.atlassian.net/browse/TEST-1, on a new tab, open the URL https://test123.atlassian.net/rest/api/3/issue/TEST-1.

• On the screen, search for the duedate field. If you find the actual value of the Due Date next to the Due Date field, then the correct field is in use. If you find the Due Date value on any other fields and value of Due Date is set to Null, then a custom field is being used in place of Due Date. In the below example, custom_field_10046 was a custom field used in place of the actual Due Date field. The real Due Date field does not have any value entered. 

• To fix the issue, 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 the same is reflected on the backlog.

• If the Due date is reflected on the backlog table, then you can remove the previously used Due date custom field from the description field as it is not the actual Due date field but a custom field with the name set to the Due date.