[Feature][Domain] Add due_date field to issues table in the issue tracking domain

[narrowizard]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Use case

Currently, Apache DevLake's issue tracking domain does not include a due_date field in the issues table. However, many issue tracking tools, such as Jira, TAPD, and ZenTao, provide a field representing the expected due date of an issue. By incorporating due_date into the domain layer, DevLake users can analyze issue deadlines across multiple tools in a unified way.

Description

We propose adding a due_date field to the issues table in the issue tracking domain. This field should be populated using default mappings from existing fields in third-party issue tracking tools:

• duedate (Jira)
• due (TAPD)
• deadline (ZenTao)

This enhancement will enable users to track and analyze issue deadlines consistently across different platforms, improving insights into project timelines, deadline adherence, and overall planning efficiency.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[narrowizard]

To further enhance the due_date field, we need to introduce a customization feature. For example, in Jira, we should add a configuration option dueDateField (similar to storyPointField). This configuration will allow users to specify which field should be used when assigning values to due_date, rather than relying solely on the default duedate field.

This flexibility will enable users to adapt DevLake to different Jira setups where the due date might be stored in a custom field. Let’s consider implementing this for other issue tracking tools as well.