DIJJI.ai Academy

Getting Started

Connect Jira

Jira is an alternative source for the issues you turn into tasks. Once Jira is connected, a project can draw its tasks from a Jira project instead of from GitHub Issues. It’s optional — GitHub Issues works on its own, and you can skip this page if Jira isn’t part of your workflow.

This page walks through making that connection. For where Jira sits among the other integrations, see Integrations: what each connection does.

Before you start

Connecting Jira is an admin action in DIJJI.ai — adding or removing the connection requires the admin role.

You’ll also need an Atlassian account with permission to authorize third-party apps on the site whose issues you want to sync (typically a site admin).

DIJJI.ai connects to one Atlassian site per organization. If your Atlassian account has access to several sites, you’ll need to choose one when authorizing — the connection will refuse to complete if more than one site is shared, and ask you to re-authorize with access to a single site.

Open the Integrations page

Select Integrations from the navigation rail. Below the GitHub card you’ll find a Jira card.

Before you connect anything, the card reads Not connected and shows the message “Connect a Jira site to sync issues into DIJJI.”

Connect Jira

  1. On the Jira card, select Connect Jira. DIJJI.ai sends you to Atlassian.
  2. Sign in if you aren’t already, and pick the site you want to share — make sure only one is selected.
  3. Review the permissions DIJJI.ai is requesting — read and write access to issues, plus offline access so the connection stays alive without re-authorizing — and select Accept.
  4. Atlassian sends you back to DIJJI.ai, which shows Jira Connected for a moment and returns you to the Integrations page.

The Jira card now reads Connected and shows the site URL (for example acme.atlassian.net) along with a health badge.

Read the connection details

The connected Jira card shows:

  • A health badge — Healthy, Degraded, or Disconnected. Healthy means the connection is working. Degraded means it’s working but needs attention. Disconnected means DIJJI.ai can no longer reach the site and you’ll need to reconnect.
  • The site URL of the Atlassian instance you authorized.
  • A last-synced time — when DIJJI.ai last refreshed data from the site, shown as a relative time like 5m ago or 2d ago. Syncing happens on its own; there’s no button to trigger it.

Label the issues you want synced

DIJJI.ai does not sync every issue on your Jira site. It only sees issues that carry the dijji label.

This is the gate you use to control which issues flow into DIJJI.ai. Apply the dijji label on a per-issue basis, or set it as a default on the boards or filters you want covered. Issues without the label are invisible to DIJJI.ai; removing the label later takes an issue back out of scope.

When you connect, DIJJI.ai also registers a webhook on your Atlassian site so it learns about new, updated, and deleted dijji-labeled issues as they change. The webhook is maintained in the background — you don’t need to manage it on the Atlassian side. No custom fields, statuses, or project changes are created on your behalf; the only persistent change to your Jira site is that webhook and the label convention you adopt.

DIJJI.ai also writes a comment back to the relevant Jira issue in a few situations — for example, when a generated plan is rejected on a run linked to that issue — so the conversation stays where your team already reads it.

Use Jira for a project

With Jira connected, the PM Tool picker on the new-project form gains a Jira option alongside GitHub Issues. Picking it lets you choose the Jira account and a Jira project from the synced list; from then on, that project draws its tasks from dijji-labeled issues in that Jira project instead of from GitHub Issues.

The PM tool is chosen at project creation. Existing projects keep the source they were created with.

Disconnect Jira

To remove the Jira connection, select Disconnect on the Jira card. A confirmation dialog opens, headed Disconnect Jira (site URL)?, with a Project dependency warning: projects using this connection will lose access to synced data, and active pipelines may be affected.

Select Disconnect to confirm, or Cancel to keep it. Disconnecting can’t be undone — you’d reconnect by going through Connect Jira again. The webhook on your Atlassian site is removed as part of disconnection.

What’s next

With Jira connected and at least one issue carrying the dijji label, you have everything a project needs to pull work from Jira. The next step is to create a project and pick Jira as its PM tool.