DIJJI.ai works best when it’s connected to the tools you already use. There are three connections that change what you can do — GitHub, Jira, and Slack. This page explains what each one is for, so you can decide what to set up and when.
You’ll find connections in two places: GitHub and Jira live on the Integrations page (reachable from the navigation rail), and Slack is set up per project under that project’s Settings pill.
GitHub
The GitHub connection is the one DIJJI.ai can’t work without. It’s how your code gets in and how finished work comes back out.
You connect GitHub once, for the whole organization. On the Integrations page, the GitHub card shows Add account — clicking it installs the DIJJI.ai GitHub app and asks you to choose which account or organization, and which repositories, to share. Once connected, the card shows how many accounts are linked, how many repositories each one has, and when they last synced.
What this gives you: when you create a project, you pick one of those connected accounts and choose a repository from the synced list. From then on, DIJJI.ai reads that repository’s code and opens pull requests against it as runs move through your pipeline. No GitHub connection, no projects — so this is the first thing to set up.
Slack
The Slack connection is optional, and it’s about staying informed rather than doing work. Connect it and DIJJI.ai posts updates about a project’s runs into a Slack channel, so you don’t have to keep the app open to know what’s happening.
Slack is configured per project, not for the whole organization — each project can notify a different channel, or none at all. Open a project’s Settings tab and find the Slack Notifications card. You connect it with a Slack Incoming Webhook URL (created in Slack itself), and you can add an optional channel name like #alerts for display. Once connected, you can send a test message, update the webhook, or disconnect it.
What this gives you: run activity for that project shows up in Slack without anyone watching for it. It changes nothing about how runs behave — it only adds a place where their progress is announced.
Jira
The Jira connection is optional. It’s a second source for the issues you turn into tasks — an alternative to GitHub Issues. If your team plans work in Jira, connecting it lets a project draw its tasks from there instead.
You connect Jira once, for the whole organization. On the Integrations page, the Jira card shows Connect Jira — clicking it takes you through Atlassian’s consent flow on the site you choose, and DIJJI.ai sets up a webhook there so it learns about issue changes. Only issues that carry the dijji label sync — that’s how you decide what flows in. Walkthrough: Connect Jira.
What this gives you: when you create a project, the PM Tool picker offers Jira alongside GitHub Issues. Pick Jira and the project will pull dijji-labeled issues from a Jira project you choose. GitHub is still needed for the code itself — Jira changes only where the tasks come from, not where the work lands.
Connection health
Each connection shows a small status so you can tell at a glance whether it’s working: Healthy, Degraded, or Disconnected for GitHub and Jira (Slack shows Active, Degraded, or Broken). Healthy means the connection is fine; Degraded means it’s working but something needs attention; Disconnected or Broken means DIJJI.ai can no longer reach it and you’ll need to reconnect.
In short: connect GitHub first — projects depend on it. Connect Jira if you’d rather pull tasks from Jira than from GitHub Issues. Add Slack per project when you want run updates in a channel.