Need to streamline workflows that involve Jira Service Management? Here's what you can expect from our integration.
Here are the fields you can currently sync with our Jira Service Management integration, and whether they can be used in rules or not.
Custom fields and other options
Our integration for Jira Service Management supports a number of custom fields and other customization settings.
The custom fields supported by this integration are Date, Text, Single-select dropdown, and Multi-select dropdown. You can also build rules with the Single-select and Multi-select dropdown fields.
You can sync subtasks with other tools that support subtasks, like Asana and ClickUp.
Default issue type
When a new Jira Service Management issue is created to match a task in another tool, you can determine which issue type will be created by default.
You can stream attachments from Jira Service Management, meaning anyone with the link can view the files without logging into this tool.
Issue numbers as prefixes
You can have a Jira Service Management issue number automatically added as a prefix to the title of a work item in another tool.
Limitations and other things to keep in mind
We're constantly looking to improve our Jira Service Management integration to support the tool's growing list of features, fields, and use cases. Here are a few limitations you should be aware of:
Administrator permissions: You need administrator permissions to connect your Jira Service Management account to Unito. Once the account is connected, you only need project-level admin permissions to create a flow.
Sprints in next-gen projects: Not currently supported.
Multi-line text fields: You can't sync these fields quite yet.
Mapping Reporter to other assignee fields: Not supported.
Syncing fix version: Currently, this can only be mapped to Text custom fields, not dropdowns or lists.
Unsupported fields: Fields that aren't currently supported by this integration include Checkboxes, Time-tracking, Story point estimate, and Voted.