...
Please note: We roll out our Jira Cloud changes in batches, delayed by up to a week, based on instance size. The update might not be available immediately for you. Jira Datacenter releases will contain all cloud changes since the latest DC release.
...
February 24, 2025 - Cloud
Features & Improvements
The bot message automation action now supports sending notifications based on Jira group custom fields
Bugfixes
Minor bugfixes to the Jira mobile app UI to improve responsiveness
...
February 17, 2025 - Cloud
Features & Improvements
Implemented a warning within the JSM Portal that we currently can’t support asset fields within Forms because of lacking API information
Added better error message when using wrong syntax within an automation
Bugfixes
Fixed some emojis bugs within Teams → displaying of custom emojis is now possible and emoji reactions are now working properly
Fixed a bug where the timefield picker wasn’t adjustable within the meetings dialogue when using danish language
Fixed a bug where it wasn’t possible to type a date into a datefield within the JSM Portal in Teams
Showing error message when a user with no active Teams/Office 365 license tries to start a Teams chat from Jira
Fixed some minor signature bugs
...
February 11, 2025 - Cloud
Features & Improvements
...
Fixed some edge case preset bugs where it was possible to have no presets
Notable changes
We introduced a Jira global permission a while back to control the visibility of the app, per user. However, this permission is not updated correctly by Jira and is causing issues for new users being added to activated projects. Therefore we have decided to make the use of the permission optional. If you have been using the Jira permission to control visibility, you'll need to enable the respective setting in the global app settings going forward
...
February 7, 2025 - Cloud
Features & Improvements
...
A new board view in Microsoft Teams, details here: Jira board view in Microsoft Teams (Upgrade of Smart Connect in Teams required)
Added support for suggesting “Incident responders” when creating a chat from a JSM incident
...