Skip to content
Start in the sandboxStart free
All connectors
Jira logo

Jira

Project & work management

Turn requests and orders into Jira work, and keep status in step across your tools.

36 ways to read, 17 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Jira with Nexra

Connected, approved, proven.

The things teams do most with Jira, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Add issue commentApproval by rule
  • Create componentApproval by rule
  • List issue attachmentsRead

Example flow

  1. Magento Open Source · Read inventoryDone
  2. Jira · Create issue or subtaskNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Jira.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Jira
  • Jira's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect a Atlassian test account before you go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Read and write Jira Cloud issues, comments, worklogs, projects, components, versions and sprints; read boards, backlog, changelogs and configuration.

Atlassian API docs
Source actions
36
Destination actions
17
Data types
27

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Attachments2
  • Get attachment metadataSource

    Metadata for one attachment; the file content is not downloaded.

  • List issue attachmentsSource

    Attachment metadata on an issue; file contents are not transferred.

Backlog1
  • List board backlogSource

    Backlog issues on a board (not in a future or active sprint), in rank order, through the enhanced backlog endpoint.

Boards2
  • Get boardSource

    One board with its type and project location.

  • List boardsSource

    Scrum and Kanban boards, optionally for one project or of one type.

Changelogs2
  • List issue changelogSourceIncremental

    Field change history for an issue, oldest first, optionally only changes since a time.

  • Bulk fetch changelogsSource

    Change histories for up to 1,000 issues in one paged request, optionally limited to some fields. Pair with Search issues on updated date for incremental history.

Comments4
  • Add issue commentDestinationNot retried automaticallyApproval before production

    Adds a plain-text comment to an issue.

  • Get issue commentSource

    One comment on an issue.

  • List issue commentsSource

    Comments on an issue, oldest first.

  • Update issue commentDestinationProvider duplicate protectionApproval before production

    Replaces the text of a comment.

Components3
  • Create componentDestinationNot retried automaticallyApproval before production

    Creates a component in a project.

  • List project componentsSource

    Components in a project with leads and issue counts.

  • Update componentDestinationProvider duplicate protectionApproval before production

    Updates a component's name, description, lead or default assignee.

Custom fields1
  • List custom fieldsSource

    Custom field definitions with types and descriptions, paged and searchable.

Dashboards1
  • List dashboardsSource

    Active dashboards visible to the API account.

Fields1
  • List fields and custom fieldsSource

    System and custom field definitions with their types, for mapping custom fields.

Filters1
  • List filtersSource

    Saved filters visible to the API account, with their JQL.

Group members1
  • List group membersSource

    Users in a group.

Groups1
  • List groupsSource

    User groups on the site.

Issue links1
  • Link issues (dependency)DestinationProvider duplicate protectionApproval before production

    Creates an issue link such as Blocks or Relates between two issues.

Issue types1
  • List issue typesSource

    Issue types visible to the API account, including subtask types.

Issues5
  • Create issue or subtaskDestinationNot retried automaticallyApproval before production

    Creates an issue; provide a parent key and a subtask issue type to create a subtask.

  • Get issueSource

    One issue with its fields, links, attachments metadata and requested custom fields.

  • List issuesSourceIncremental

    Issues in a project ordered by last update, including subtasks, links and requested custom fields.

  • Search issues (JQL)SourceIncremental

    Searches issues with the enhanced JQL search, using a query Nexra builds from validated filters.

  • Update issueDestinationProvider duplicate protectionApproval before production

    Updates supplied fields on an existing issue. Omitted fields are unchanged.

Priorities1
  • List prioritiesSource

    Issue priorities, optionally for some projects.

Projects4
  • Create projectDestinationNot retried automaticallyApproval before production

    Creates a project from a template with a key, name, type and lead. Permission, notification and security schemes are left at their defaults.

  • Get projectSource

    One project with its lead, category and issue types.

  • List projectsSource

    Projects visible to the API account.

  • Update projectDestinationProvider duplicate protectionApproval before production

    Updates a project's name, description, lead, default assignee or URL. The key and schemes are not changed.

Remote links2
  • List remote linksSource

    Links from an issue to records in other systems, such as orders or tickets.

  • Create or update remote linkDestinationProvider duplicate protectionApproval before production

    Links an issue to an external record. A link with the same global ID on the issue is updated instead of duplicated.

Sprint issues1
  • List sprint issuesSourceIncremental

    Issues in a sprint, through the enhanced JQL search.

Sprints4
  • Create sprintDestinationNot retried automaticallyApproval before production

    Creates a future sprint on a Scrum board.

  • Get sprintSource

    One sprint with its state, goal and dates.

  • List board sprintsSource

    Sprints on a Scrum board, optionally by state.

  • Update sprintDestinationProvider duplicate protectionApproval before production

    Partially updates a sprint's name, goal or dates. Starting and completing sprints are not performed.

Statuses1
  • List statusesSource

    Workflow statuses with their category, globally or for a project.

Transitions2
  • Change issue statusDestinationNot retried automaticallyApproval before production

    Performs exactly the named transition (by ID from List available status transitions), with an optional resolution and comment.

  • List available status transitionsSource

    Workflow transitions the API account can perform on an issue.

Users2
  • List usersSource

    All users on the site, including app users, for assignee and owner mapping.

  • Find usersSource

    Active users matching a name or email fragment, for assignee mapping.

Versions4
  • Create version (milestone)DestinationNot retried automaticallyApproval before production

    Creates a project version with optional start and release dates.

  • Get versionSource

    One project version with release state and dates.

  • List versions (milestones)Source

    Project versions with release dates, used as milestones.

  • Update versionDestinationProvider duplicate protectionApproval before production

    Updates a version's name, description, dates, or released and archived state. Unresolved issues are not moved.

Watchers1
  • List issue watchersSource

    Users watching an issue.

Worklog changes1
  • List changed worklogsSourceIncremental

    IDs and update times of worklogs changed since a time, across the site, for incremental time-tracking sync.

Worklogs3
  • Log workDestinationNot retried automaticallyApproval before production

    Records time spent on an issue.

  • List worklogsSource

    Time logged against an issue.

  • Update worklogDestinationProvider duplicate protectionApproval before production

    Changes the time, start or comment of a worklog; the remaining estimate adjusts automatically.

Access and limits

Authentication
Atlassian account email and API token
Plans and access
All Jira Cloud plans, including Free. Boards, sprints and backlog need Jira Software. Results follow the permissions of the Atlassian account that owns the API token. Creating and updating projects needs the Administer Jira global permission.
Test environment
Free Jira Cloud sites and Atlassian developer sites can be used for testing.
Rate limits
Cost-based points and burst limits per tenant; HTTP 429 with Retry-After.
Pagination
startAt offsets for most collections; nextPageToken for the enhanced JQL search, enhanced backlog and bulk changelog fetch; a since timestamp for changed worklogs.
Provider events
Jira webhooks for issue, comment, worklog, project, version and sprint events; webhooks with a secret are signed with X-Hub-Signature (sha256= hex HMAC of the body). Flows can start the moment something happens: when an issue is created; when an issue is updated; when an issue is deleted; when a comment is added.

Before you build a flow

  • Attachment metadata is read; file contents are not transferred or uploaded.
  • Descriptions and comments are converted between plain text and Atlassian Document Format; rich formatting is not preserved.
  • Issue, comment, worklog and sprint creation have no provider idempotency key; uncertain creates are not repeated automatically.
  • Issue search builds JQL only from validated filters (projects, types, statuses, priorities, labels, people, sprint, version, component, dates and simple text); free-form JQL is not accepted.
  • Sprint updates change name, goal and dates only; starting, completing and swapping sprints and moving issues between sprints and the backlog are not performed.
  • Deletes, archiving projects, permission, notification and security schemes, group membership changes, watcher changes, bulk issue operations and user management are intentionally excluded.
  • The legacy Agile sprint-issue and backlog endpoints are deprecated; Nexra uses the enhanced JQL search for sprint issues and the enhanced /rest/software/1.0 backlog.

Developer reference

  1. Create the Atlassian credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Jira, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Atlassian docsAPI referenceAtlassian docsAuthenticationAtlassian docsRate limitsAtlassian docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/jira and the Connections API.