You opened an issue in GitHub and expected it to show up as a task in DIJJI.ai — but the Tasks page is empty, or the issue just isn’t there. This page walks through the reasons, most common first.
For how syncing works when it’s working, see Where tasks come from.
First: there is no Sync button
DIJJI.ai watches your connected repository on its own. Issues become tasks automatically, usually within seconds — there’s no manual sync step and no Sync button to press. If you’re hunting for one, stop: the absence is expected, not the problem.
1. The issue isn’t labelled dijji
This is the cause almost every time. DIJJI.ai only picks up issues that carry the dijji label. An issue without it is ignored, however it’s worded.
Open the issue in GitHub and check its labels. If dijji isn’t there, add it — the match is case-insensitive, so dijji, Dijji, and DIJJI all count. The task appears on the Tasks page shortly after the label lands.
This applies to old issues too. Adding the label to an issue filed months ago, even a closed one, syncs it just the same — the label is what counts, not when the issue was created.
2. The repository isn’t bound to a project
DIJJI.ai only watches repositories that a project is built on. If no project in your organization uses that repository, its issues have nowhere to land.
Check that a project exists for the repository, and that the project was set up with GitHub Issues as its source. A project pointed at a different repository — or one set up for Jira — won’t pick up these issues. See Create a project for how a project is tied to a repository.
3. The GitHub connection is degraded or disconnected
If your organization’s GitHub connection has dropped, DIJJI.ai stops hearing about new issues. Open Integrations and check the GitHub connection’s health. If it reads degraded or disconnected, reconnect it — see Read integration health states for what each state means and Disconnect or reconnect an integration for the fix. Once it’s healthy again, new issue activity flows through.
4. Give it a moment
Syncing is quick but not instant. DIJJI.ai learns about an issue from GitHub, so there’s a short delay between labelling the issue and the task appearing. If you’ve just added the label, wait a few seconds and refresh the Tasks page before assuming something’s wrong.
Still nothing?
If the issue carries the dijji label, the repository is bound to a GitHub Issues project, and the connection is healthy — but the task still hasn’t appeared after a few minutes — reach out to DIJJI.ai support. Include the repository name, the issue number, and roughly when you added the label.