Tasks alongside development
GrigTasks works independently. The separate grigdesk-tasks-driver package will connect it to an existing GrigDesk workspace.
The integration is part of the first-release plan and is not yet offered as a ready-to-install download on this site.
The connection process
- Install the tracker and configure HTTPS.
- Create a personal API token with the required projects and scope.
- Install the driver package in GrigDesk.
- Enter the API address and token in connection settings.
- Explicitly link a tracker project to a GrigDesk project if your workflow needs it.
Project names and identifiers are not matched automatically.
Driver capabilities
| Action | First-release plan |
|---|---|
| Read, create and edit tasks | Planned |
| Comments, checklists and tags | Planned |
| Review, return and reopen | Through existing GrigDesk actions |
| Delete | Checked against tracker permissions |
| Attachments | Available in the tracker’s own web interface and API |
| Arbitrary custom transitions | Available in the tracker’s own web interface and API |
| Timer and analytics widgets | Outside the first release |
When the tracker’s web interface is enabled, a card link can open the task there.
Connectivity differences
The driver safely retries within a single call. The existing GrigDesk contract does not support a promise to recover a manual retry after a client restart or compare against a long-open form.
The durable queue and its states belong to the tracker’s own web interface.
Product boundaries
The connection does not require changes to GrigDesk pipelines, inboxes, video or browser features. Accounts and permissions belong to the tracker server; agent workflows remain in GrigDesk.