Project creation requires startDateTime/endDateTime, not startDate/endDate

[asachs01]

Bug

autotask_create_project returns HTTP 500 when using the documented startDate and endDate parameters. The Autotask API fields are actually startDateTime and endDateTime (ISO 8601 format).

Details

The tool schema advertises:

• startDate (string, YYYY-MM-DD)
• endDate (string, YYYY-MM-DD)

But the Autotask REST API expects:

• startDateTime (datetime, ISO 8601: 2026-04-01T00:00:00Z)
• endDateTime (datetime, ISO 8601: 2026-06-30T00:00:00Z)

Also, projectType is a required field (picklist: 2=Proposal, 3=Template, 4=Internal, 5=Client, 8=Baseline) but is not included in the tool schema.

Reproduction

// This fails with 500:
autotask_create_project({
  companyID: 588,
  projectName: "Test",
  status: 1,
  startDate: "2026-04-01",
  endDate: "2026-06-30"
})

// This works via execute_tool:
autotask_create_project({
  companyID: 588,
  projectName: "Test",
  projectType: 5,
  status: 1,
  startDateTime: "2026-04-01T00:00:00Z",
  endDateTime: "2026-06-30T00:00:00Z"
})

Expected Fix

1. Either map startDate/endDate to startDateTime/endDateTime internally, or rename the parameters
2. Add projectType to the tool schema as a required field

Impact

Project creation fails unless using execute_tool bypass with correct field names.

[github-actions]

🎉 This issue has been resolved in version 2.15.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀