Admin Set-up and Global Configurations
Implementation Planning
How to use
Personal Settings
User Connection Guide
Personal Notifications
App Home Screen and Settings
Advanced Personal Notifications
Channel Settings
Additional Features
Creating a JIRA Issue from Slack
Dedicated Slack Discussion Channels for Jira issues
Use Slack Actions to create Jira issues
Quick Create Jira issues
Get Jira issue details in direct messages
Auto expand Jira issues when mentioned in Slack
How to Schedule Reports
Add a comment from Slack
Use the global action in Slack to create Jira issues
Use workflow builder to create Jira issues
Use workflow builder to add comments to Jira issues
Slash Commands /jira-plus
Use commands (CLI) interface to create and update Jira issues.
Assign Jira issues in Slack
How to capture Slack messages in Jira Issues
Attach files in Slack to issues in Jira
Mobile Compatibility
Assign Tickets to Yourself Using the :eyes: Emoji
Interacting with Issues using the View Dialog
Quickly Log Time to Jira Issues
Hosting
Billing
Security
FAQ
What is a bot id? How can I find it?
How do I stop getting notified for my own actions?
Is my data secure and protected?
How do permissions work? How is Jira access controlled?
How to resolve a SSL certificate issue
How do I delete messages from the Integration+ Jira bot?
New static IP addresses
Connecting to behind the firewall Jira instances.
How do I disable Jira emails and replace with Slack messages?
How does user attribution work? Are actions in Jira going to be the correct user?
Atlassian Marketplace Billing
Webhooks
Set up with Service Accounts
Nextup Help Centers
- All Categories
- Security
- Technical Overview
Technical Overview
Updated
by Nick Cron
Integration+ connects your team in Slack to your ticketing software in Jira. Here's how it works from a technical perspective.
High-level summary
- Slack makes API calls to our services in AWS when events are triggered
- Our services make API calls to Slack to send messages, react to button clicks, etc
- Our services make API calls to Jira to read and write data
- We use OAuth flows
Initial Connections
- Add the bot to Slack and allow the required permissions to start the process
- Provide your Jira URL and connect to your Jira instance
- Create an application link in Jira (NOTE: This requires administrator permission)
- Complete the OAuth flow to allow access to the application link
Example Flow
This example shows you the process and API calls that occur to help you better understand the technical process.
Use Case: User sends a message to a support channel in Slack
- A User sends a message to a channel configured for automatic request creation.
- Slack sends a message to our systems based on the Events API
- We validate the message is from Slack using best practice
- Our system processes the payload by retrieving configuration data from our database.
- Our system makes a call to the Jira REST API to create the issue
- Our system makes a call to Slack to send a message to the channel to confirm the issue has been created.
Slack Communication
- All communication is API based
- Slack makes API calls to our systems. These calls are verified to be authentic via signed secrets.
- We make API calls to Slack over HTTPS with OAuth
Jira / JSM Communication
- Communication is API and webhook based
- Jira sends data via webhooks to our systems
- We make API calls to Jira over HTTPS with OAuth
Security
Read more about our security here.