Jira Integration

The Jira integration connects DevStride to Jira Cloud so you can import Jira projects into DevStride and keep them synchronized. Once configured, issues, comments, issue links, and sub-tasks stay aligned across both platforms.

Setting up Jira is a two-stage process: first you create a Credential and connect a Jira site, then you map that Jira site's projects and issue types to your DevStride data model.

To reach the integration, open Settings from the lower-left corner of the platform, then choose Integrations from the header. The list on the left includes Credentials, GitHub, Slack, Microsoft Teams, Azure DevOps, and Jira.

Before you start

• You need access to Settings > Integrations, which is part of your organization settings.
• The Atlassian account you connect must grant the manage:jira-project scope. Only sites that grant this scope appear as connectable accounts.
• To enable complete two-way sync, you must be a Jira admin, because the issue-link webhook has to be created manually in Jira (see Enable two-way sync).
• Two-way sync runs only while your DevStride subscription is active. Webhook-driven updates are skipped when the subscription is inactive.

1 - Create a credential and connect Jira

Credentials store the authentication DevStride uses to talk to Jira.

1. Go to Settings > Integrations > Credentials. The page is headed Manage authentication credentials for integrations.
2. Click Add to open the Add Credential dialog.
3. Enter a Label to identify the credential (for example, John Doe's JIRA).
4. Set Provider to Jira.
5. Click Create. An Atlassian OAuth popup opens; complete it to authorize DevStride.

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 to enable two-way sync. Choose Connect to get started to begin.

2 - Configure projects and mappings

Once a Jira site is connected, open Settings > Integrations > Jira. Each connected Jira instance appears as an expandable section showing its base URL, along with these controls:

• Webhook Setup — opens the guide for enabling two-way sync.
• Raw config — view the underlying configuration.
• Save changes — save your mapping configuration.
• A Configuration / Import Jobs toggle to switch between mapping setup and import history.
• Disconnect and + Connect another organization.

Select projects to set up

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.

Map each enabled project

For every enabled project, set the following:

• Status Collection — Select a Status Collection that should be used to set up the boards for this project.
• Workstream — Select a Workstream where the items for this project should be placed. This is the parent Workstream into which imported items land.

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:

• Statuses — map your Jira board columns to DevStride board statuses.
• Custom Fields — map your Jira fields to DevStride custom fields.
• Tags — map your Jira labels to DevStride tags.
• Priority Levels — map your Jira priorities to DevStride priority levels.

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.

3 - Import a project

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.

Enable two-way sync

Importing brings issues into DevStride, but keeping issue-link changes flowing both ways requires a webhook in Jira. DevStride cannot create this issue-link webhook automatically, so a Jira admin must add it manually.

1. In the connected Jira instance section, click Webhook Setup to open the Jira Cloud Webhook Setup Guide.
2. Follow the guide to create a webhook in Jira Cloud named DevStride Issue Links Integration.
3. Subscribe the webhook to the Issue link: created and Issue link: deleted events.

Once the integration is active, DevStride keeps work synchronized using these Jira events:

• Issue created, updated, and deleted
• Issue link created and deleted
• Comment created, updated, and deleted

Webhook deliveries are verified

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.

Working with imported items

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:

• A message such as This item was imported from JIRA (or This workstream houses items imported from JIRA at the workstream level).
• View source item — deep-links to the original issue in Jira.
• Sync — triggers a manual synchronization of the item.
• Item Metadata, including the Jira URL.
• A reminder that local changes are overwritten by source updates.

Imported items are read-only in DevStride until two-way editing exists: 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.

Disconnecting

You can disconnect at the project or instance level:

• Disabling a project, or disconnecting a Jira installation or credential, prompts you to choose how existing items should behave.
• Because imported items are linked to their Jira source, disconnecting after an import can remove or detach data in DevStride. Review the disconnect options carefully before confirming.

If the connection's access is revoked

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 Settings → Integrations → Jira 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.

Related

• GitHub