Jira is a proprietary issue tracking product developed by Atlassian which allows bug tracking and agile project management.
Changelog
21 versions
v4.0.0
Latest
- Breaking changes: existing Jira connections must be re-authenticated after this update due to changed OAuth scopes.
- CreateProject, UpdateProject, DeleteProject: narrow scope from the broad manage:jira-configuration to manage:jira-project (the dedicated project-admin scope, sufficient for create/update/delete project).
- UpdateProject: add read:jira-work for the GET project fallback used when permission-scheme updates are forbidden on Free plans.
- Added MakeApiCall component for performing arbitrary authorized API calls to the Jira API.
v3.1.0
- Added test() (Flow Test Mode) to all triggers: NewIssue, UpdatedIssue, NewProject, DeletedProject (polling) and NewIssueWebhook, UpdatedIssueWebhook, DeletedIssue, NewProjectWebhook, UpdatedProject, DeletedProjectWebhook. Shared jira-commons.fetchLatestIssue/fetchLatestProject reuse the same search/project requests as tick() (newest-first, no `> now` baseline); webhook variants reshape the record into the webhook payload via toWebhookShape.
v3.0.1
- Added output examples to component schemas.
v3.0.0
- Breaking changes: existing Jira connections must be re-authenticated after this update due to changed OAuth scopes.
- Fix OAuth scopes: auth.js now only requests offline_access, component-specific scopes are declared per component.
- DeleteProject: fix scope from write:jira-work to manage:jira-configuration.
- GetInstanceInfo: add missing scope read:jira-work.
- ListTemplates: remove unnecessary scope (private component, no API call).
v2.0.3
- CreateIssue, IssueMetadata: add pagination support for createmeta endpoints — required fields (e.g. Summary) were missing in inspector when projects had more fields than the default page size (50).
v2.0.2
- Create Issue, Update Issue: fix support for custom fields.
v2.0.0
- (breaking change) Updated FindIssues, NewIssue, and UpdatedIssue components to use the new JQL enhanced search API endpoint instead of the deprecated /rest/api/3/search endpoint.
v1.4.0
- Added new component - Get Instance Info: Retrieves information about the Jira instance.
- Use svg icon instead of png in all components.
v1.3.0
- Auth: when creating a new connection, there is an option to specify the JIRA Cloud Site.
v1.2.2
- CreateProject, UpdateProject, AssignIssue: fixed "Cannot read properties of undefined (reading 'includes')" error.
v1.2.1
- Auth: remove npm dependencies from the auth.js.
v1.2.0
- Find Issue Transitions: The new component allows you to find available issue transitions either by searching for them by name or by listing all available transitions.
v1.1.0
- UpdateIssue: add update status field. The status can only be selected from the list of available options after entering the Issue ID or Key, as the status is dependent on the specific issue. Alternatively, you may directly enter the status ID.
v1.0.8
- CreateProject: updated tooltip.
- CreateIssue, UpdateIssue: Assignee field now only display assignees available for the project in the selection. The endpoint used for creating fields of both components has been updated to no longer use the deprecated one.
v1.0.7
- UpdatedIssue: fix onTick error.
v1.0.6
- NewIssue, UpdatedIssue: now works with timezones correctly.
v1.0.5
- Fixed issue with JIRA API scopes when obtaining reporters.
v1.0.4
- Fixed issue with JIRA API scopes when obtaining labels.
v1.0.3
- Updated links to JIRA documentation to open in new tab.
v1.0.2
- IssueMetadata fix.
v1.0.0
- Initial version
Authentication
| Type | Details |
|---|---|
| OAuth 2 |
Authentication Hub
Verified
This connector is globally authenticated and verified by Appmixer and is ready to use without registering your own OAuth application with the provider. Appmixer's Authentication Hub acts as an authentication proxy, so all OAuth-based connectors work out of the box. You can still use your own OAuth credentials (clientId and clientSecret) for enhanced customization or compliance — see the Connector Configuration section of the documentation. The Authentication Hub is enabled for all hosted Appmixer tenants; on self-managed installations it has to be explicitly set.
Scopes:
offline_access
read:me
|
Triggers
10
Updated Issue
Triggers when an issue is updated. Issues that are updated after 1 minute of its creation are considered updated.
Additional Scopes:
read:jira-work
Updated Issue Webhook
Triggers when an issue is updated (Webhook).
Additional Scopes:
read:jira-work
Deleted Project
Triggers when a project is deleted.
Additional Scopes:
read:issue-type:jira
read:project:jira
read:project.property:jira
read:user:jira
read:application-role:jira
read:avatar:jira
read:group:jira
read:issue-type-hierarchy:jira
read:project-category:jira
read:project-version:jira
read:project.component:jira
Deleted Project Webhook
Triggers when a project is deleted (Webhook).
Additional Scopes:
read:issue-type:jira
read:project:jira
read:project.property:jira
read:user:jira
read:application-role:jira
read:avatar:jira
read:group:jira
read:issue-type-hierarchy:jira
read:project-category:jira
read:project-version:jira
read:project.component:jira
New Project
Triggers when a new project is created.
Additional Scopes:
read:issue-type:jira
read:project:jira
read:project.property:jira
read:user:jira
read:application-role:jira
read:avatar:jira
read:group:jira
read:issue-type-hierarchy:jira
read:project-category:jira
read:project-version:jira
read:project.component:jira
New Project Webhook
Triggers when a project is created (Webhook).
Additional Scopes:
read:issue-type:jira
read:project:jira
read:project.property:jira
read:user:jira
read:application-role:jira
read:avatar:jira
read:group:jira
read:issue-type-hierarchy:jira
read:project-category:jira
read:project-version:jira
read:project.component:jira
Updated Project
Triggers when a project is updated (Webhook).
Additional Scopes:
read:issue-type:jira
read:project:jira
read:project.property:jira
read:user:jira
read:application-role:jira
read:avatar:jira
read:group:jira
read:issue-type-hierarchy:jira
read:project-category:jira
read:project-version:jira
read:project.component:jira
Actions
14
Get Instance Info
Retrieves information about the Jira instance including version, build details, server time, and health status. This component is useful for getting basic server information and verifying instance connectivity.
Additional Scopes:
read:jira-work
Make Api Call
Performs an arbitrary authorized API call to the Jira API.
Additional Scopes:
read:jira-work
Create Project
Create a project in Jira. It does not work on Cloud Free Plan accounts.
Additional Scopes:
write:project:jira
read:project:jira
Get Project
Get a selected project using its ID.
Additional Scopes:
read:issue-type:jira
read:project:jira
read:project.property:jira
read:user:jira
read:application-role:jira
read:avatar:jira
read:group:jira
read:issue-type-hierarchy:jira
read:project-category:jira
read:project-version:jira
read:project.component:jira
List Projects
Get a list of projects.
Additional Scopes:
read:issue-type:jira
read:project:jira
read:project.property:jira
read:user:jira
read:application-role:jira
read:avatar:jira
read:group:jira
read:issue-type-hierarchy:jira
read:project-category:jira
read:project-version:jira
read:project.component:jira
Update Project
Update a Jira project. It does not work on Cloud Free Plan accounts.
Additional Scopes:
read:issue-type:jira
read:project:jira
read:project.property:jira
read:user:jira
read:application-role:jira
read:avatar:jira
read:group:jira
read:issue-type-hierarchy:jira
read:project-category:jira
read:project-version:jira
read:project.component:jira
write:project:jira
write:project.avatar:jira