An integration connects a company to the system where development happens and shows on its issues what goes on there: branches, commits, pull requests and their states.
What every integration has in common
- Read only. Quevell never writes to the outside system: comments, labels and statuses all stay here. So an automation rule triggered by an integration event can never set off another event in that integration.
- The company connects, each project chooses. Anyone with the "Edit company settings" permission can connect a system in Administration. A project's repositories are picked in its settings by anyone who manages access to the project.
- Linked by issue key. Quevell reads branch names, pull request titles and commit messages, finds issue keys in them and links each match to its issue. The key must belong to a project that watches the repository.
- People appear under the names the outside system uses. A commit author is shown as recorded there and does not become a Quevell user.
- Search covers issues. QQL queries issues; branches and commits appear on the issue they are linked to.
- Delivery bodies are erased once read. Each delivery is erased as soon as Quevell has read it, and the personal token used to confirm the right to install the app is never stored.
- Unlinked stays unlinked. Every link has an "Unlink" button. Once it is used, events about that pull request or branch no longer attach to the issue until someone links it again by URL.
The systems
| System | What it reads |
|---|---|
| GitHub | Branches, commits, pull requests, reviews, checks |
The next system becomes a new page of this section and a new row of this table.