Reference
Supported trackers
Passback files each comment in one of these ten trackers; the page Connect a tracker has the steps.
| Tracker | What a comment becomes | Attachments | How you give access |
|---|---|---|---|
| Linear | A task per comment. | The file is uploaded to the task. | Approve Passback in your browser, or paste a personal API key. |
| Plane | A work item per comment in one project. | The file is uploaded to the work item. | The workspace slug and an API key. |
| GitHub | An issue per comment in one repository. | A text file is added as a collapsed comment. A binary file cannot be attached, so the screenshot is a link. | Install the Passback GitHub App in your browser, or paste a token. |
| Azure DevOps | A work item per comment in one project. | The file is uploaded to the work item. | The organization name and a personal access token. |
| GitLab | An issue per comment in one project. | The file is uploaded to the issue. | An access token with the api scope. |
| Trello | A card per comment in one list. | The file is uploaded to the card. | An API key and a token. |
| Notion | A page per comment in one database. | The file is uploaded to the page. | An integration secret, and the database shared with the integration. |
| Asana | A task per comment in one project. | The file is uploaded to the task. | A personal access token. |
| Jira | An issue per comment in one project. | The file is uploaded to the issue. | Approve Passback in your browser. |
| ClickUp | A task per comment in one list. | The file is uploaded to the task. | A personal API token. |