Use the Jira integration when a team's work already lives in Jira Cloud and you want it visible and reportable in DevStride without re-keying it. DevStride imports the Jira projects you choose and keeps the imported items in step with Jira: issues, comments, issue links, and sub-tasks.
Setup has two stages: create a Credential that connects a Jira site, then map that site's projects and issue types onto your DevStride data model and import.
To reach the integration, open Configure Settings → Integrations. The Integrations group lists Credentials, GitHub, Slack, Microsoft Teams, Database Access, Identity Providers, Jira, and Azure DevOps. You need Manage Integrations to see the Jira and Credentials entries.
Credentials store the authentication DevStride uses to talk to Jira.
After authorizing, each Jira site you have access to appears in the Credentials list. Use Connect to install DevStride on a site; once installed, the action shows Connected, and you can use Configure or Disconnect as needed.
If you open the Jira page before connecting a site, you will see a Connect Jira prompt inviting you to connect your Jira account. Choose Connect to get started to begin.
Once a Jira site is connected, open Configure Settings → Integrations → Jira. Each connected Jira instance appears as an expandable section showing its base URL, along with these controls:
Under Select Projects to Setup, toggle each Jira project on or off. Only the projects you enable are configured for import. Enabling a project expands it so you can configure its mappings.
For every enabled project, set the following:
Then, for each entry in the Jira Issue Types column, choose the DevStride Item Type the issue type should map to, and configure the mapping sub-sections:
Mapping is defined per Jira issue type, so each issue type can resolve to its own Item Type and field mappings.
Below the project list, the Global Mappings section holds User Mapping (Map your Jira users to DevStride users), which applies across all projects.
When your mappings are ready, click Save changes.
After saving your mappings, click Initiate import for a project to bring its issues into DevStride. Imports run as jobs that you can track under the Import Jobs tab.
If you change a project's mappings after it has already been imported, DevStride prompts you to optionally re-import that project so the changes take effect.
Sync is one-way, from Jira into DevStride. Importing brings issues into DevStride, but keeping issue-link changes flowing in requires a webhook in Jira. DevStride cannot create this issue-link webhook automatically, so a Jira admin must add it manually.
Once the integration is active, DevStride keeps work synchronized using these Jira events:
The webhooks DevStride registers when it imports a project carry a per-registration secret in their callback URL, and every delivery is checked against it before anything is written — a POST that does not present the right secret is refused and nothing in your organization changes. You do not manage this secret; DevStride mints a fresh one each time it registers a project's webhooks, and importing (or re-importing) a project rotates it. Projects imported before this check existed keep syncing as they always have; re-import such a project to move it onto a verified registration.
Jira sub-tasks sync into DevStride as sub-items. If a Jira issue changes from a standalone issue into a sub-task, DevStride removes the original work-item link and creates the corresponding sub-item link.
When an item has been imported from Jira, it shows an imported from JIRA badge (a down-arrow icon). Selecting the badge opens a popup with:
Imported items are read-only in DevStride: you can open their relationships and blocker panels, follow the board link, and view everything, but adding or removing relationships, setting a blocker, and other edits stay blocked.
You can archive a sprint board, or the folder of boards a Jira project created, from its menu in Plan Delivery. DevStride never recreates it, and the sync carries on past it: the sprint import skips an archived sprint, and an issue in that sprint is placed on the project's board instead, as an issue with no sprint is. Unarchive the board or folder and its sprints take issues again, with no second board made. See Boards and folders synced from Azure DevOps or Jira.
You can disconnect at the project or instance level:
If the Jira credential's authorization expires, or someone revokes it in Jira, DevStride tells you so directly: you'll see a message asking you to reconnect the integration to restore access, rather than a generic failure. Reconnect the credential in Configure Settings → Integrations → Credentials and syncing resumes.
DevStride only remembers what Jira successfully returned, so once access is back it is picked up on the very next request. A moment of lost access no longer leaves Jira screens failing for hours afterwards. What DevStride remembers is also kept separately for each Jira site, so two sites never see each other's issue types or fields.
list_integration_installations, create_integration_installation, and submit_integration_job work with the same Jira installationsDatabase Access for BI Tools
Generate read-only PostgreSQL credentials, connect Metabase, Tableau, Power BI, or any SQL client to your organization's data, and keep the credentials current as tables change.
API Keys
Create and manage API keys for programmatic access to DevStride, audit and revoke every member's keys as an administrator, and know the rate limits and the API vocabulary changes.