GitHub
Link a pull request to a task. Checks and reviewers render on the item.
Integrations
Git on the task. Email from the platform.
Pull requests and merge requests sit on the same record as status and reviewers. Invites go out through the email adapter. Tokens stay with administrators.
Source control
The pull request stays on TASK-102.
GitHub and GitLab link the branch, the checks, and the reviewers to the work. The delivery engineer does not hold org-wide credentials. Administrators keep those on the backend.
Automation
When status changes, run the next step.
Review assigns Sprint 18 and notifies QA. Resolved clears remaining hours. Turn a rule off until the Git merge path is ready. The list of rules lives in the workspace.
What ships
GitHub, GitLab, and email.
Those are the connections Flagship Tracker ships. Slack, Salesforce, and a public marketplace are not in the product.
GitLab
The same task-level link for GitLab merge requests. Credentials stay with administrators.
Platform mail for invites and notifications, configured by administrators.
Need Git connected in a first tenant? Contact sales.
Ready to connect Git?
Get started in a workspace, or contact sales if an administrator needs to provision credentials.