Fields, startDateTime and dueDateTime of TodoTask are being set incorrect where it is neglecting the time part.

Open

#2,278 opened on Jan 23, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: java
Domain: api

Research direction

No source file or test is named. Start by reproducing creation and modification of a TodoTask with startDateTime and dueDateTime in Graph Explorer and SDK 6.14.0, then trace the SDK's TodoTask datetime handling. Done means both fields preserve the supplied time component consistently with reminderDateTime and completedDateTime.

Written by the indexing model from the issue text.

Description

status:waiting-for-triage type:bug

Describe the bug

While creating or modifying a task item, the fields startDateTime and duedatetime of todotask are being set incorrectly while this is not the case for other datetimetimezone datatype fields like reminderDateTime and completedDateTime. Feels more like a backend issue as tried with graph explorer as well. please check the attached screenshot for reference.

Expected behavior

Fields startDateTime and dueDatetime should be set correctly.

How to reproduce

just try to create/modify a todotask item with startDateTime or dueDateTIme fields, you would observe a discrepancy there.

SDK Version

6.14.0

Latest version known to work for scenario above?

I have checked in graph explore so i didn't check in the latest but pretty sure it is the case.

Known Workarounds

no workarounds

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_

Dominant language: Java
Stars: 444
Forks: 154
Avg merge: 18h 28m
Merged PRs (30d): 4

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Compatibility certification request for FJ-EAP 2.1.0 for Jakarta EE Platform 11 Open

certification

Difficulty 1/5 Under an hour Newbie friendliness 80/100

jakartaee/platform#1359 · Opened Sep 24, 2026
Python guide test runner copies stale Micronaut Test Resources state Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

micronaut-projects/micronaut-guides#1856 · Opened Sep 23, 2026
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Open

bug ecr

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

floci-io/floci#4264 · Opened Sep 23, 2026
Drop point numbers from GitHub milestones Open

Needs: Triage Type: Feature request

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

AntennaPod/AntennaPod#8794 · Opened Sep 23, 2026
[aw] Issue Classification Agent timed out Open

agentic-workflows

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

github/copilot-sdk#2760 · Opened Sep 23, 2026

More Java issues