FAQ
At the moment the service is only available for Atlassian Cloud installation. Bitband explores options to release hosted version of Slack-Jira.
It’s on the roadmap but not yet available for public distribution.
Unfortunately, this integration is only available for Jira Cloud. We are considering building a Server version in the future.
It's on our roadmap, but not available at this time.
All you need is just to invite people to Slack with all activities. You need their emails and then you can set their names, options and channels available to them.
When you’ll create notifications in Slack Jira Integration you’ll see the list of users and then you can invite anyone to your channel/notification.
Added users need to confirm the access to your workspace by clicking on the confirmation link sent to their emails. Then users can see all available channels and use commands for getting the information, for example, /jira get (tickets key like TEST-1).
Yes, our Slack Jira Integration supports multiple Slack workspaces.
Yes. Jira notifications are configured at the issue (ticket) level, project, or for the entire system (instance) of your Jira. Many of our user's set up rules for each project based on specific types of Jira issues and specific events for those issues they want to be notified about inside Jira. The Filter tab allows you to select which types of Jira issues inside a project (or instance) you want to send notifications for. You can even use JQL to filter down to very specific types of issues. On the events tab, you can select which types of activities (events) on a Jira issue you want to send a notification for. So there's no need to have notifications for every issue and every event - you'll want to pick the things that really matter to your team.
You can find it when configuring a channel under "Jira Filters".
There are several ways of how to accomplish this. You can pick one of them:
- Deactivate appropriate values in “Filters” menu using “Basic filter” or “Advanced JQL filter” modes (“Notifications” → “Configure” → “Jira Filters”).
- Disable events update type in the channels menu (“Notifications” → “Configure” → “Jira Events”).
For “Issue channels” it’s possible to disallow any notifications using the appropriate control “Allow Slack notifications from individual JIRA issues” (“Issue Notifications"→ deactivate switch on top).
You can also mute entire channels in the "Notifications" tab "Status" column.
Yes, when configuring the notifications type in the name of the Slack channel you would like the notifications sent to. You can also select private channels. Note, for private channels, you'll have to have connected the app with an admin account that has access to send messages to private channels.
You can create notifications to automatically send notifications to a specific Slack channel anytime new issues are created that meet the filter/event criteria you set. However, at this time you cannot automatically spawn a new Slack channel that's specific to that one new issue. You'll have to manually go into that Jira issue and use our app settings to connect to a new Slack channel.
We are adding this functionality and it will be available soon.
This is currently not available, but it's something currently under development.
Currently this option is not available but Bitband Team is working on providing a solution for this use case.
Here are a list of common issues and how to workaround them.
- 1.Open the Slack Jira Integration apps
- 2.If Slack is not connected, click the “Sign In” button and log in Slack
- 3.Go to the notifications tab
- 4.Make sure channels are connected
- 5.Go to any connected channel
- 6.Make sure filters and events that you need, are enabled
The following reasons are the most probable cause of the malfunctioning - insufficient permissions and incorrect configuration.
- Firstly, check if a Slack account used for integration has administrative privileges. If an account with regular permissions was used then disconnect it and complete the steps described in Slack Jira Integration Getting Started.
- Secondly, check that Slack channels used in the Add-on configuration are still exist.
Once Slack and Jira properly integrated the channel settings should be revised for possible misconfigurations. Validate all existing channels for “Filters”, “Events” and “Options” configurations.
If the issue is still unresolved contact Bitband Support Team: [email protected].
As it is recommended in “Slack-Jira Integration in Details” section systems pairing better be accomplished using separate Slack account with administrative privileges.
This is rare problem which has very simple solution - just reload the frame by pressing right mouse button on the page area and choosing appropriate option from the browser's menu. Usually, it has identical name.
As an alternative solution you can reload the whole page. Use next keyboards shortcuts:
- Chrome/Chromium: on Windows OS press Ctrl+R; on macOS - Cmd+Shift+R.
- Firefox: on Windows OS press Ctrl+F5; on macOS - Cmd+Shift+R.
- Edge/Internet Explorer: on Windows OX press F5 or Ctrl+R.
or use appropriate option in the browser's menu.
This error appears if you try to use issue types that are not activated in Jira. Review and enable necessary issue types in project settings. You can find appropriate settings following the next path:
"Open the project - "Project Settings" - "Issue Types" - "Add Issue Type" - select (or create) issue type - press "Add" button". Now the issue type should be accessible from slash commands.
It's recommended you create a dedicated Slack admin user that's solely used for connecting this app from Jira to Slack. If you use a Slack admin account that's actively used by someone they'll end up receiving some system notifications inside their Slack which could be annoying to their daily workflow.
There are two possibilities: permissions or configuration. Check that you used a Slack admin user when connecting the app to Slack. If you didn't, try disconnecting the app and re-connecting as an admin. After that check your notification configuration. You need to select which issues you want to include/exclude from notifications and what events you want to cause notifications. You can do this inside a Jira issue, at the project level, or system level. It's possible you aren't including any issues to send notifications.
Last modified 7mo ago