Jira gives users a simple way to organize and plan the release of any software. This allows development teams to lay out key steps to follow when releasing the software including 'Plan', 'Track','Release','and Report' to guide users.
With Workato, you can keep projects and issues in sync between Jira and other issues or tickets tracking apps used by other departments such as Zendesk, ServiceNow, Salesforce's Desk.com.
The Jira connector uses Jira Cloud REST API V2.
Supported editions and versions
The Jira connector works with Jira cloud instances and Jira on-premise instances from 7.x onwards.
How to connect to JIRA on Workato
The Jira connector uses basic authentication to authenticate with Jira.
- Connection name
Give this Jira connection a unique name that identifies which Jira instance it is connected to.
- On-prem secure agent
To connect to on-premise Jira instances, set up the on-premise agent. Ability to use the on-premise access functionality depends on the Workato plan subscribed to.
- Host name
Complete Jira instance URL used to login to Jira.
Username to connect to Jira.
Password to connect to Jira.
- Enable firewall-friendly IP
Relevant for organizations with IP whitelisting. Select yes to have all requests from Workato originate from a consistent, known IP address.
Roles and permissions required to connect
JIRA users can connect to JIRA from Workato. We recommend that a separate user be created for integration purposes.
There are 3 main ways a user can have access to objects:
- People roles in Project Settings
- Issue security Schemes
- Permission schemes
If the JIRA user does not have accesss to an object through any of these methods, the object cannot be retrieved from the JIRA project, and will instead return a '403 - Forbidden' error.
People roles in Project Settings
Users can be added to a project by selecting Project Settings → People. Each user can be assigned 1 or more roles:
- Service Desk Customers
- Service Desk Team
Permissions to each role vary and can be configured in JIRA. Hence, JIRA users connecting from Workato must be added to the project with the appropriate roles to use relevant actions, i.e Create issue, Update issue, etc.
Issue Security Schemes
Issue security schemes can be created and added to each project, allowing control over who can view and edit the issues of the project.
If a project has issue security schemes, the JIRA user connecting from Workato must have access to the project’s issues in order to use Workato triggers and actions related to issues.
Permissions can be granted for specific actions like creating issues, edit issues, assign issues, etc. Permissions can be found by selecting Project Settings → Permissions.
Each permission can be granted across:
- Applications (JIRA and JIRA service desk users)
Available roles are Developers, Administrators, Service Desk, Service Desk Customers and Service Desk Team. If permission scheme is defined for any of these roles, the JIRA user connecting from Workato must also have the same role(s) to use particular actions, i.e Create issue, Update issue, etc.
For permissions across Applications, Any logged in user permission must be granted to use the Workato triggers and actions.
For permissions assigned to Groups, the JIRA user connecting from Workato must be a member of the selected group to use the triggers and actions. Selecting Anyone grants access to all the users.
To use upload and download attachment actions, the JIRA user connecting from Workato must be added to the permissions under the Attachment Permissions tab of the permissions page.
Comments triggers and actions
To use triggers and actions relating to Comments, the JIRA user connecting from Workato must be added to the permissions under the Comments Permissions tab of the permissions page.
Issues triggers and actions
To use triggers and actions relating to Issues, the JIRA user connecting from Workato must be added to the permissions under the Issues Permissions tab of the permissions page.
Working with the Jira connector
Using real-time triggers
To use Jira real-time triggers (which registers a Jira webhook via the API), the authenticated user needs to have the Jira Administrators global permission. To set up real-time triggers without requiring the Jira Administrators global permission, use the HTTP connector, New event via webhook trigger to set up a Jira webhook trigger via the Jira admin console.