[Bug][ZenTao] Projects with planned dates of 'long-term' in ZenTao may cause remote scopes interface errors

[yu501954162]

Search before asking

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

What happened

What happened
Projects with planned dates of 'long-term' in ZenTao may cause remote scopes interface errors. The error message is as follows: parsing time "\u957f\u671f" as "2006-01-02T15:04:05Z07:00": cannot parse "\u957f\u671f" as "2006"

What do you expect to happen

Please add processing logic for long-term planned dates

How to reproduce

1.Change the planned date of a project in ZenTao to 'long-term' and save

2.After adding the ZenTao connection, click on Details

3.Click the Add Data Scope button on the Details page

4.Check the error interface

Anything else

ZenTao version is 21.4

Version

v1.0.3-beta1@2ef56cf

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

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

[dosubot]

The error happens because DevLake's ZenTao plugin tries to parse all planned date fields as ISO8601 dates, but 'long-term' (e.g., "长期") is a special string in ZenTao that isn't a valid date. The parser expects a date and fails when it encounters this value, causing the remote scopes interface error you described. There is currently no logic in the codebase to handle or sanitize non-date values like 'long-term'—they are passed directly to the date parser, which throws an error when it can't parse them (source, source).

A practical solution would be to add logic in the ZenTao plugin to detect and handle special values like 'long-term' before attempting to parse them as dates. For example, you could treat these as nil or ignore them, so the parser only receives valid date strings. This would prevent the error and allow projects with indefinite planned dates to be processed gracefully.

No recent pull requests or documentation address this issue, so this would be a new improvement for the ZenTao integration.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[yu501954162]

@d4x1

[GoSimplicity]

I will submit a pr to solve this problem.