--- title: "Archive" canonical: "https://support.appfire.com/space/JIFS/683739990/Archive" format: markdown --- > Macro (aura-html) > ℹ️ Note: Only public-availability releases are listed below. > ⚠️ Important Legacy Workflows deprecation notice from Slack > ⚠️ > ⚠️ Slack has announced the deprecation of Legacy Workflows, and has decided not to provide a method for apps to continue providing workflow steps. If you are using any Workflow Steps from Jira Integration+, you will no longer be able to create new workflows after June 24th 2024, and no longer be able to run these workflows after September 26th. Please reach out to Slack with any questions. **[Learn More](https://slack.com/help/articles/16787711643411-Legacy-Workflow-Builder-deprecation)**. # 2025 Releases ## 6.12.3 **December 5th** - Fixed a bug that prevented a global webhook from being re-created on Jira 10 if it was deleted from Jira. ## 6.12.2 **November 13th** - Fixed a bug where some text-based commands for issue search would return no results even when there were matching issues. - Fixed a bug where an issue could not be created from a Workflow Builder manifest when the Assignee field was not on the Create screen in Jira. - Security fixes. ## 6.12.1 **October 31st** - **Features:** - Links to Jira comments are now automatically expanded to show the author and comment text in Slack. - Follow Updates and Sync Thread actions can now be automatically enabled for all issues created in a channel. - Added support for the `comma_separated` function to be used in Workflow Builder manifests with multi-select values. - Channels are now notified when an issue is created from their Welcome message. - **Fixes and improvements:** - Improved notification performance for organizations with multiple workspaces. - Fixed an issue where some organizations had a false positive warning about global webhook health on Jira 10. - Fixed an issue where users couldn't connect to a different Jira when the currently connected one didn't have a valid product license. - Fixed an issue where changing the Main Authorized User wasn't available if the current one had been deactivated in Jira. - Fixed several issues with converting Slack text formatting to Jira. - Fixed a rare bug where the wrong key could be detected and expanded in Slack when an issue from a project with a similar key was mentioned. - Security fixes. ## 6.11.3 **August 7th** - Fixed issue where scheduled notifications at 5m/30m intervals were not sent to users. - Fixed issue where webhooks were not functioning properly in Jira 10.5 DC instances. - Fixed issue with Follow Updates where users could receive duplicate notifications. - Fixed issue where notifications were being sent for restricted Jira issues. - Security fixes. ## 6.11.2 **July 3rd** - Improved support for users migrating from “Notifier by Appfire” to Jira Integration+ for Slack. - Fixed creating issues from workflows where the assignee or reporter is not available. - Security fixes. ## 6.11.1 **June 12th** - Security fixes. ## 6.11.0 **June 5th** - Jira admins can now completely turn off the Create Discussion Channel panel for DC instances. - Added support for users migrating from “Notifier by Appfire” to Jira Integration+ for Slack. - Fixed issue where quotes were causing problems in Workflow Builder 2.0 manifests. - Security fixes. ## 6.10.0 **April 30th** - Now connecting to Jira from Slack is a far more streamlined process. - Fixed issue loading Legacy Workflows after enabling Workflow Builder 2.0 support. - Fixed issue where default reporter could be wrong for emoji created issues. - Fixed some bugs and generally improved the new Catch Up feature. - Security fixes. ## 6.9.2 **March 31st** - Connect-on-Forge release for Jira Cloud. ## 6.9.1 **March 17th** - Fixed issue where Slack channels were not properly created from Jira post functions. - Security fixes. ## 6.9.0 **March 17th** - Send Slack messages from Jira workflows using our new Jira post function. - See what you’ve missed out on using the new Catch Up feature on our Home tab. - Fixed issue where synced threads were being synced as our main authorized user. - Security fixes ## 6.8.3 **March 4th** - Fixed issue executing Slack Workflow Builder 2.0 functions in socket mode. - Fixed issue where Create Discussion panel in Jira was not loading. ## 6.8.1 **January 30th** - Fixed issue editing the Create Jira issue step in Slack Legacy Workflow Builder. ## 6.8.0 **January 22nd** - Added support for Slack Workflow Builder 2.0 for Jira Data Center. - Fixed issue with creating discussion channels from Jira tickets. - Security fixes. # 2024 Releases ## 6.7.0 **December 17th** - Custom domains in Jira are now supported in all our Slack products - Added the ability to directly comment on tickets during transitions. - Fixed an error when creating dedicated discussion channels for Jira tickets. - Fixed issue with user notifications not being properly cached. ## 6.6.2 **November 20th** - Fixed issue where creating dedicated channels was not respecting default global settings. - Fixed issue where Slack oauth could hang when installing bot from the Account Portal. ## 6.6.1 **November 7th ** - Live bi-directional thread syncing is now available between Integration+ and Jira! - Create escalation channels in Slack using newly supported Jira post functions. - Track changes to specified Jira labels using Slack channel notifications. - Bot messages can now trigger CLI commands. - CLI commands will now translate @mentions into Jira users. ## 6.5.2 **October 11th** - Fixed issue where the Slack connect empheral message was not getting delivered. ## 6.5.1 **October 1st** - Small bug fixes ## 6.5.0 **September 25th ** - New onboarding experience for new users, including a revamped Slack app home wizard. - Personal Advanced Notification Settings have been added to Integration+ app home settings in Slack! - Fixed formatting for some comments captured via emoji. - Fixed a bug with Slack synchronized channels that prevented Priority from being added to the name when it was set as a variable. ## 6.4.0 **September 12th ** - Jira Integration+ is now an Enterprise Ready Slack app! This means it can be [installed Org-wide](https://appfire.atlassian.net/wiki/spaces/JIFS/pages/684163573). - The Integration+ Jira app now has a Connected Workspaces page that will show you all of your connected Organizations and Workspaces, allow you to make changes and add additional. - Resolved an issue that prevented Discussion Channels from linking to the issue in Data Center environments. - Fixed an issue preventing users from turning Slack Discussion Channels back on after they were disabled. - Enterprise (Self-Hosted) customers can now use our marketplace Slack app ## 6.3.1 **August 26th** - Security fixes ## 6.3.0 **August 20th** - A custom message (including @ mentions) can now be added to channel notifications - Added field configuration support for message unfurl or self-hosted customers - Added a Slack workspace switcher to the account portal for self-hosted customers - Fixed a bug that would cause errors when custom fields contain extremely large amounts of data - Fixed a couple of bugs with CLI commands and attachment uploading ## 6.2.2 **July 19th** - Small bug fixes ## 6.2.1 **July 8th** - Added an optional Description field to Reports, which supports @mentioning users or groups when a report sends - Brand new, much more user-friendly onboarding process (which you are unlikely to need if you are reading these release notes.) - Fixed type-ahead search for the “Teams” field in Jira Data Center. - Fixed an issue so that the “Sprint” field in Slack messages will now be a link even if the Sprint is completed. - Fixed a bug that added broken attachments to Jira issues created using the message action in channels without the bot. (We are still unable to add these attachments to Jira due to Slack permissions, but now we are sending an error message and no longer adding a broken attachment.) ## 6.1.0 **May 30th ** - Linked Issues are now displayed in the Issue Detail View modal the same way that we display Sub-tasks - Fixed a bug with URL formatting in issue summaries. - Fixed a bug that could send the same attachment to Jira twice in certain thread scenarios. - Fixed a bug that would result in failing to add an attachment to Jira in certain thread scenarios. - Fixed a couple of related Quick Create bugs that can prevent the creation of issues in some default field scenarios. ## 6.0.0 **May 14th ** - Linked issues are displayed in the Issue View dialogue - **[New Feature Release]** Field configurations allow full field-level control of notifications, issue detail views, and more, globally, by project, and in channels and personal notifications - see the documentation [here](https://appfire.atlassian.net/wiki/spaces/JIFS/pages/759497382) - Improvements to batched notifications - It is now possible to save workflows in Slack that involve Integration+ - Updated channel welcome message when adding the bot to a channel for the first time - The Edit modal now displays the Story Points field - Adding time to an issue no longer results in an incorrect timestamp being applied to the ticket - Multiple users with identical display names will now have the username added to dropdown selectors for differentiation ## 5.17.1 **May 3rd** - Improvements to internal logging - Rebranding fixes - Updated help documentation links to use short links ## 5.17.0 **February 29th** - Using the CLI option to quick create no longer fails silently if there are default values for any of the Quick Create fields ## 5.16.7 - The Slack message dialog now correctly loads when capturing information to an existing issue - Typeahead search now correctly works for the "Team" field on Datacenter installations - Unauthorized users can no longer review channel configurations using the `jira-plus configure` command - Several security fixes ## 5.16.5 - Clicking reconnect on the account portal now correctly saves the new connection data ## 5.16.4 - Discussion channels can now be configured by the channel creator whether or not they have global channel configuration access ## 5.16.3 - Security fixes # 2023 Releases ## 5.16.1 - Security fixes - Enhancements to Slack Workflow Builder functionality - The “Create a Jira Issue” message action now works correctly in channels without the Integration+ bot - Dedicated Discussion Channel welcome message now updates correctly when the issue is modified - Enhanced multiline command support - Webhooks now correctly update when users edit or delete channels --- ## 5.14.0 - Assignees and Watchers will now be notified when issues are moved to a new project - It is now possible to Auto-Archive Slack Discussion Channels when Jira Issues are resolved - Fixed an issue that prevented ticket expansions for Slack messages that include attachments - Improvements to `jira capture` command and use of the 📍 emoji to create Jira issues - Improvements to the way we handle Blocked Projects - Fixed some inconsistencies with the 📷 functionality - Fixes for the “Asset Objects” field - Fixed an issue that could cause scheduled reports to be sent at the wrong time - Various security fixes --- ## 5.13.8 > ⚠️ **Ecosystem Change: **Integration+ billing has migrated to the Atlassian Marketplace. - Improved response time of various models - Corrected an error that would sometimes cause notifications not to be sent - Long (2000+ character) comments captured from Slack now render correctly in Jira - Fixed an issue that could cause an infinite loop when trying to authorize with the bot - Implemented deduplication in the team selection settings of the home tab - Fixed an issue where Slack messages would sometimes be added to Jira issues with incorrect timestamps - Attachments are now correctly added to a ticket when using Quick Create - Footer messages for created issues can now be customized - There is now an Account Portal setting to disable attachment uploads from Slack - Custom footer enabled for issues created using Workflow Builder - An error caused during issue editing no longer replaces the edit modal - Time estimation fields now displayed in the issue creation modal - The "Sprint" field no longer displays on issues of type Sub-task - Custom JQL is now correctly reflected in the channel notifications modal --- # 2022 Releases ## 5.12.0 - Implemented support for Insight and Label Manager fields in Slack workflows - Improved error handling for failed steps in Slack Workflows - Jira Character limitations are now respected in all fields - Enabled notification for large attachments - Added the "Unassigned" option to the assignee dropdown - Updates to text formatting, including bold and italics and long hyperlinks - Required fields can now be set individually as defaults when configuring Quick Create - Report scheduling now succeeds even if the previous report failed - Date/Time and Date-Time pickers are now able to be used in Quick Create - Using the /jira-plus link command now respects the synching settings from the account portal - Threads can now be captured even if the authoring user has been deactivated - Report filtering now respects ordering by priority