Task trackers
Keep tasks inside GrigDesk or connect an external tracker. The shared board identifies each task's source, and its card connects the requirements to assessment and pipeline work.
Supported trackers
| Tracker | Connection | Scope |
|---|---|---|
| GrigDesk | Built in; no driver installation. | Local tasks, project, assessment and pipeline. No external portal. |
| Bitrix24 | Separate grigdesk-b24 package. | Token or username and password, where the portal allows that authentication method. |
| Jira Cloud | Separate grigdesk-jira package. | Jira Cloud address, email and API token. This package does not claim Jira Server or Data Center support. |
| Customized Bitrix24 | A driver for the specific portal protocol. | The grigdesk-b24-discript implementation targets particular customizations, rather than every self-hosted portal. |
Install external packages separately. The source list helps choose a repository; an installable version is checked during installation. The shared board keeps internal tasks alongside one selected external tracker.
Install and configure a tracker driver
Internal GrigDesk tracker
Choose New task and enter a title, description and project. The project must have a configured profile and published routes to be selectable. Tasks are stored on the GrigDesk server; no external account is needed. Assessment starts separately from the card, rather than when saving a task.
You can favorite internal tasks, put them on the shelf and open them in a pipeline. They remain accessible when the external tracker fails. Portal timers, comments, completion and reopening are not part of the internal card.
External tracker capabilities
A driver declares actions such as task creation and editing, comments, timers, attachments, labels and metrics. Account permissions also apply. Different trackers provide different capabilities.
For example, Bitrix24 supports comments and timers. Jira Cloud supports comments, labels and workflow transitions, but not timers or attachments. Custom portal metrics belong to its driver and are not promised for every connection.
The screenshot shows an example board with Bitrix24 tasks. Follow selected work in pipelines and keep a personal selection on the shelf.
Case: self-hosted Bitrix24
Suppose your company hosts Bitrix24 and has customized task statuses, time tracking, reports or HTTP handlers. If the standard API remains compatible, try the standard driver first. Self-hosting alone does not require a new package.
If the protocol or behavior differs, you can build a custom tracker driver. It adapts the portal API to the GrigDesk contract, declares supported operations and returns task card data and numeric widgets. This does not require modifying the application's source code.
The grigdesk-b24-discript driver follows this approach: it integrates a customized portal's session authentication, /local/ajax/ handlers and /salary/ data. Check and adapt that protocol before using it with a different portal.