Current documentation coverage
The initial website documents issues and views, projects and cycles, timelines and initiatives, project releases, comments and Inbox, manual customer feedback, administration, and API, MCP and Webhook integrations.
Project releases include planned, released and cancelled states, one current target per issue and independent publication snapshots. MCP reuses personal API keys and existing authorization for issue and directory tools. Timelines use real independent dates; Insights keeps insufficient historical measures unknown. Each guide explains behavior and limitations. Optional features depend on instance configuration.
This entry describes documentation coverage, not a claim that development completion dates are production release dates. Before the first publication, the operator must verify that the application commit referenced by the website is deployed.
This candidate revision clarifies workspace selection and batch member addition. Demo acceptance or a local commit is not a production release.
This candidate improves page transitions: team sections keep search, loading and retry stay in the body, saved views follow browser history, and temporary next-page failures keep verified records available for retry. Existing access checks remain in force. Local acceptance is not a production release.
Comment webhooks include resource IDs so receivers can locate the issue, project, or project update and read the comment. Historical deliveries retain their original payloads.
Identify the version
Every page shows its application revision in the footer. Open release metadata for application and website commits, the documentation content hash, build time and release status. Website build time is not the time a database migration or production rollout completed.
An in-application project release records your team’s delivery. It is not an Autodone software version and cannot prove application deployment. Without an explicit deployment record, a version name is not release evidence.
Future updates
Feature, permission and workflow changes include Chinese and English guide updates in the same change. API changes maintain the shared OpenAPI contract. CI checks language pairs, navigation, links and impact declarations; reviewers check meaning. Automation cannot determine whether a written explanation is accurate.
Website releases pin commits and verify application health and the deployed revision. A mismatch stops publication. Editorial fixes may publish separately while remaining linked to the running application revision. The two services are not atomically deployed: failures retain the previous website for retry and do not automatically roll back the database.
For each subsequent user-visible release, append bilingual notes describing changes, impact and limitations rather than pasting an internal commit list.