New Sciple is live. Connect your AWS in 10 minutes and explore the platform with a sandbox workspace. Book a demo
sciple

Jira integration

Connect your Atlassian Jira Cloud instance to Sciple. Once wired up, Jira issues and per-project breakdowns show up on the home dashboard, on a dedicated projects tab, and on a per-project page with status, priority, and assignee summaries.

What you get

  • Home widget. Total open issues with a To Do / In Progress / Done split, scoped by your default JQL query.
  • Projects tab. Every Jira project you can see, listed in one place.
  • Project dashboard. Per-project stat cards, a by-priority bar chart, a by-assignee bar chart, and a filterable issue table.
  • Issue table. Key, summary, status pill, assignee, priority, and last-updated. Each row links out to the issue in Jira.

Prerequisites

  • A Sciple workspace where you have the settings.manage permission.
  • Access to a Jira Cloud site (any *.atlassian.net URL).
  • An Atlassian account that can read the projects you want to surface.

Step 1. Create the Jira credential

In the dashboard, open Manage and go to Credentials. Add a new credential of kind username_password with provider type jira. The username is your Atlassian email. The password is an API token, not your Atlassian password.

Generate an API token at id.atlassian.com/manage-profile/security/api-tokens and paste it into the credential value. The token is encrypted at rest in your AWS Secrets Manager backend and is never returned in API responses or logs.

Step 2. Connect Jira

Open Manage, go to Integrations, and pick Jira. Fill in the form:

  • Name. A display label for this connection, for example My Jira.
  • Base URL. Your Jira Cloud URL, for example https://your-domain.atlassian.net.
  • Credential. Select the Jira credential you created in Step 1.
  • Default JQL. Optional. A JQL query applied to the home widget and the default issue list. Example: assignee = currentUser() ORDER BY updated DESC. If you leave this blank, Sciple uses updated >= -30d ORDER BY updated DESC so queries stay bounded.

Click Test connection. A green badge confirms the connected account email. Click Save. The configuration is persisted and an audit event is written in the same database transaction.

What syncs

Sciple pulls data from Jira on demand whenever a user opens one of the surfaces above. There is no background sync, no webhook ingestion, and no data is pushed back to Jira. The integration uses Jira REST API v3 to fetch:

  • Issues (key, summary, status, status category, assignee, priority, updated).
  • Projects (key, name, lead, project type, avatar).
  • Approximate match counts for JQL queries (used by the home widget).
  • Account info from /myself, used only during the connection test.

Permissions and audit

Read endpoints (viewing the home widget, the project list, project summaries, and issue lists) require dashboard.view. Write endpoints (creating, updating, or deleting the Jira configuration) require settings.manage.

The actions JIRA_CONFIG_CREATED, JIRA_CONFIG_UPDATED, and JIRA_CONFIG_DELETED land in the same audit log as the rest of the platform, in the same transaction as the change. The credential reference is recorded; the API token value never is.

Limits

  • Read-only. Sciple does not create issues, transition statuses, or post comments back to Jira.
  • One Jira connection per workspace. A workspace can wire up a single Jira Cloud site.
  • No in-platform issue detail page. Clicking an issue key opens the issue in Jira in a new tab.
  • Charts sample 100 issues. By-priority and by-assignee breakdowns on the project dashboard are tallied from the most recent 100 matching issues, not the full result set.
  • Health is on-demand. Connection health is recorded the last time you ran a test. There is no background health check.

Removing the connection

Open Manage, go to Integrations, pick Jira, and click Remove. The configuration is deleted and an audit event is written. The credential is not deleted; you can reuse it for a new connection or remove it separately from Credentials.

What is next

  • Access and audit covers how permissions and the audit trail work across every integration.
  • API reference documents the HTTP routes that power this integration.