- Help Center
- Using Unito
- Advanced Use Cases
-
Get Started With Unito
-
Using Unito
-
Items in Sync, Account Management, and Billing
-
Troubleshooting and FAQs
-
Data Privacy & Security
-
Integration Documentation
- Airtable
- Azure DevOps
- Basecamp
- Bitbucket
- ClickUp
- Confluence
- Eloqua
- Favro
- GitLab
- HubSpot
- Intercom
- Jotform
- Mailchimp
- MeisterTask
- Microsoft Excel
- Microsoft Outlook
- Miro
- monday.com
- Notion
- Pipedrive
- PostgreSQL
- Slack
- Snowflake
- Stripe
- SurveyMonkey
- Teamwork
- Typeform
- Xero
- Zendesk
- Zoho Projects
- MySQL
-
Atlassian Jira Integration Docs
-
Trello Power-Up Docs
-
2-Way ServiceNow Integration
-
Asana Integration Docs
-
Google Integration Docs
-
Salesforce Integration Docs
-
Wrike Integration Docs
-
Azure DevOps Integration Docs
-
Smartsheet Integration Docs
-
GitHub Integration Docs
How to Build Rules With Issue Type
For integrations like Jira and GitHub, Unito is able to use issue type in rules. Here's how to set it up.
Unito's ability to use issue type in rules
For some connectors, like Jira and GitHub, you can create rules that filter synced issues depending on their type.
For GitHub, you can choose to sync only Issues, PRs, or both.
For Jira you can choose to sync all issue types or select from among these: Bug, Epic, Improvement, New Feature, Task.
How to build rules with issue type
If you only want to sync a specific type of issue, you can build a rule that filters out all other issues. All you need to do is go to the rules screen — either by editing an existing flow or creating a new one.
Then, click on the Add a new trigger dropdown.
After that, click on Issue type. Here's what you'll get.
From there, you can use the Select a value dropdown to pick the type of issue you want to sync. Note that you can select more than one.
Pick an issue type and you'll have successfully built your rule!
Now, this flow will only sync Jira issues that have the Bug type that have been created after November 8th.