What's new
Follow new features and improvements to Troopr HelpDesk here.
Slack threads with Jira Thread Sync will now be customized to show only comments or comments and activities.
- Improved handling of auto-create functionality when the Slack message has more than 255 charactersTicket previews will not generate again when Slack message is updated
- Personal notifications will now link to customer portal rather than to project
Ticket preview (Unfurl) behaviour can now be customized for every channel.
- Tickets created from Slack conversations are now attributed appropriately.
- Fixed issues with Chinese language request types in ticket creation
- Fixed a bug in the ticket creation command in the bot channel
- Fixed a bug that in some cases blocked the CSAT survey message after the ticket is resolved
- Fixed a bug that prevented Ticket card update status action from working
- Emoji Task It will now show the appropriate message to invite Troopr to channel
You can now customize the emoji you use to create issues from Slack messages.
- Jira Notification for @mention now uses full name instead of display name
- Slack onboarding now greets with a display name in place of the full name
- Customers can now request a change of subscription plan
Troopr products are now billed separately. Customers can get the benefit of lower prices when buying individual products. See pricing page for more details.
- Date time picker field not showing value in edit mode
- Channel admins can now see all configured channels even when they are not members of said channels
- Disabled Slack link previews in all Troopr messages by default
- Moved "Start thread sync" to the top in jira actions dropdown
- DM channel ticketing feature out of beta. Customers can enable by default in personal pref page
- Fixed a bug that caused ticketing approval message to not work in some cases
- Jira Server connection time out error will take only 10sec
- Fixed minor bugs in Pricing page UI
- Handled API throttling to limit Jira and Slack API calls when loading web app, to keep within limits
New Channel Preferences page UI shows channel type for clarity.
- Channel configuration can now be deleted in channel preferences main page
- Fixed a bug that caused project search in support channel ticket creation form to not work
- Internal comments will also show in the agent channel for Jira Server and Cloud
- Troopr now tracks install metadata to provide a custom onboarding experience
- New slack channel onboarding
- Customers can now enable/disable each of the 5 products
- Custom onboarding is available now for each of the 5 products
- Metrics page now moved from Home to Metrics tab
- Customers can restrict access to enabling /disabling Troopr products for the workspace
- Restrict Channel configuration - fixed bug that sometimes showed wrong admins in UI
Troopr now lets you configure a channel to automatically create tickets for every message posted.
- Fixed a bug which caused thread sync to not work in some cases
- @mention notification will not be delivered when user does not have access to the project
- Minor performance improvements for Jira notification delivery
- The "Jira Login" button in Slack now takes the user directly to the Atlassian page for authorization
- Fixed formatting issues in rendering issue description
- Fixed a bug in thread sync when triggered from the ticket list
- Multi-message Task It - Troopr now populates the message poster user name from Jira
- CSAT acknowledgement message now shows the submitted feedback clearly
Customers now receive a feedback survey in Slack for every ticket that is resolved. They can rate the service by choosing the emoji directly from Slack.
- Fixed issues that prevented some users from receiving @mention Jira notifications in Slack.
- Minor performance improvements to Jira notifications.
- Fixed issues in a few customer channels that reported “Start thread sync” for individual messages even when the channel setting was enabled.
Some IT requests have additional transitions in the workflow with the approval step allowing approvers to take decisions even before the agents can proceed with the requests. The approvers now receive notification to make a decision (approve/decline) in Slack.
- Fixed issues that prevented some users to see recent comments in the Slack thread.
- Users now receive a ticket update notification message in the dedicated Slack thread when the agent changes the status of the ticket (from Jira or Slack).
- Fixed issues that prevented some users from accessing the app home.
You can now set ticket creation defaults for public and private channels. Set any type/number of fields from the ticket creation form as defaults. This configuration is available in the Channel preferences page.
- Fixed issues that prevented some users from adding comments in the multi-message actions
- Minor fixes in workspace admin access functionality
- Minor improvements in the “user mapping” modal
- Minor UI enhancements in the web app
- Fixed issues that prevented Troopr to be added in some channels where the number of users was greater than 100
You can now choose to raise requests on behalf of others. This field is available in the ticket creation modal.
- Minor enhancements in ticket creation and edit modal
- Multiple bug fixes and minor UI improvements in the web app
- Fixed issues that prevented some users from receiving an acknowledgement message when their Jira accounts were not verified
- Minor UI enhancements to Jira onboarding modal
You can now set defaults for ticket creation in DM’s and private conversation with “Troopr Assistant”. This configuration is available on the Personal preferences page.
- Fixed issues that prevented some users from creating tickets when channel defaults are not configured
- Minor fixes in Jira ticket search and unfurl actions
- Fixed issues that prevented some users from configuring Jira notifications in Slack
You can now enable/disable channel level thread sync as part of the Jira notification subscription configuration. When thread sync is enabled, ticket creation/updates in Jira will start a thread in Slack where further discussions will be actively synchronized with Jira. Read more about channel notification configuration.
- Fixed issues that prevented some users from performing Jira unfurling in Slack
- Made minor improvements to multi-action attachment
- You can now set a channel for support as a part of channel settings in Slack
- Ticket view now shows all the important fields in Slack
- Made improvements to Jira server onboarding
You can now create Jira tickets from Slack messages using a simple ticket emoji. Read more about ticket creation here.
- Added the request type field in the ticket creation form
- Fixed issues with automatic user syncing from Slack and user mapping to Jira
- New lines in Slack messages are handled during quick ticket creation
- Made minor improvements to the search command in Slack
- Admins can now sync users from Slack manually
- Jira bot now supports “update status” and “add comment” commands in Slack
You can now set your preferences for Thread Sync and Unfurl under settings. This setting is available on the Connection settings page.
- Comments in the threads show complete text without truncating
- Fixed webhook issues in the Slack grid for Jira cloud
- Fixed issues with the “Custom report” for JQL configuration for all the Jira Service Desk projects
- The thread sync functionality is now working across all the workspaces in the Slack grid
- The Report creation form will now show a warning message when JQL has more issues than the Report limit
- Fixed issues with the Channel reports & nudges webpage
- Multiple bug fixes and UI enhancements in web app and settings
- Fixed issue with “channel reports & nudges” run now option
- Multiple enhancements in ticket listing, creation and edit modal
- You can now choose to set up personal notifications for “Issues reported by me”
Now you can view the Jira tickets with issue details, attachments, comments and frequent actions all in one place.
- Fixed issues with Slack user profile update sync failing in some scenarios
- Fixed "Issues by Reporter" report to handle cases when the number of reporters is high
- Fixed Jira ticket status update to also update the corresponding comment in Jira
- Troopr web app - paginated lists now allow page size configuration
- Task it message action in Slack handles rich text formatting better
- Reduced verbosity of messages in Thread Sync
Jira notifications can now be posted in the Slack thread allowing for a more compact notification format and less noise in the channel. The Slack thread can also be configured to auto-sync future updates from Jira to Slack and vice versa. This can be a better way to track and monitor tickets in Slack. These options are now configurable in the notification subscription configuration.
You can now open Jira issues in view mode similar to the opening issue in the Jira web app. This action will open a popup with all the issue details organized for easier consumption. It will also contain shortcuts to relevant actions. Check out by clicking on View action in a Jira ticket card in Slack.
- Now you can submit feedback on Troopr from the web app (similar to how it is done in Slack)
- Fixed an issue where channel list count was showing incorrectly in the dashboard
- Fixed an issue with timezone updates in Slack not syncing with Troopr user profile
- Improved search behaviour in Find action and during /t find
- Fixed an issue with default values not populating in list field types sometimes
- Channel configuration in the Troopr web app will now show who set it up
Troopr usage metrics are now available in the Troopr web Dashboard. This includes the number of active users, activity and others in the current and past 30 day periods.
- Recent Comments in Thread Sync should show recent up to 5 public comments
- Fixed issues with syncing profile updates for the new members from Slack to Troopr
- Disabled auto unfurling of block kit links to external websites for subscription status messages
- Troopr will attempt to mark Slack message sender as requestor during the "Task It" action
- Thread Sync can now be started or stopped in any Slack (ticket card) message
A Cleaner and more organized sidebar allows more space for content and scales better for upcoming new features in Troopr.
Now Jira service desk agents can convert multiple messages in DM channel conversation to Jira ticket and also start an active sync thread that continuously and automatically updates the Jira ticket with the Slack conversation. The feature is in Beta. Request the team (hello@troopr.io) for early access.
- Jira charts now perform consistently in high load scenarios
- Jira comments form now shows most recent on top
- Jira thread sync now handles permission issues during comment updates gracefully
- Jira notifications now support when a comment is added alongside an attachment
- Jira notifications now show longer comment text before truncating
- Jira notifications now handle comments with visibility restrictions better
- Jira notification subscription form will now warn about existing subscriptions
- Slack user name, profile pic updates now auto-sync into Troopr
- Jira Unfurl now works on edited messages in Slack
- Jira thread sync feature now alerts relevant users during updates
- Troopr workspace switcher in web app shows workspaces list in alphabetical order
Now you can configure the ticket creator to automatically be assignee based on channel preference.
Customers can now set their own help desk link if they have their own getting started material for their team. This setting is available on the Feedback settings page. This will update the links to Help docs everywhere within Troopr.
- Fixed a Report bug that caused failures in high load scenarios.
- Channel configurations don't show up sometimes in the list in the web app.
- @mention in Slack now will render properly in Jira comment and description
Thread Sync - Delete the comment in Jira now syncs into active thread
- Unfurl now defaults to thread mode in all-new workspaces
- Ticket listing filters now show if filters are applied over and above the default channel project
- Task it action behaviour in thread updated
- Dashboard reports (creation & editing) always checks if the user has verified his Jira account
Now you can choose how Troopr expands context when Jira issues are mentioned in Slack. You can also completely disable this behaviour. See configuration in the Connection page for details.
You can now choose to sort the list of tickets that show up when you type /t list or in the Slack app home. Troopr will also remember the settings per channel. Try it in any channel to see how it works.
- Users can now reset channel settings for channel
- Thread Sync now supports @mention formatting
- Thread Sync now supports comment edits updates from Jira
- Fixed bug where some channel configurations won't show in the channel preferences page
- The User mapping page now shows the count of users who have the verified account
- User mapping page allows filtering in user mappings table
- The Ticket creation form now loads faster
- New users in Slack workspace will now be auto mapped to linked Jira account
- "User Mapping" page now accessible only by admins or connection owner
- Jira notification fix - when the user changes the status & comments at the same time, comment notification is no longer missed
Troopr now supports 2-way real-time ticket syncing in Slack. Conversations in an active thread in Slack will become comments in Jira for the linked tickets. Any update to the ticket in Jira will also show up in the thread, always and in real-time.
Users navigating across workspaces in Slack Grid will now have a more seamless experience
- Troopr shows shared channel reports in all relevant workspaces in Grid
- Troop shows shared channel configuration in all relevant workspaces in Grid
- Troopr auto-syncs user preferences across workspaces in the Grid
These features are in addition to the Jira admin and user connection configuration propagation across workspaces in Grid released earlier.
- Troopr Launcher - minor design changes for easier accessibility of frequent actions
- Multiple bug fixes in ticket listing and notifications
The new Troopr web Dashboard page will be the default landing page. Other than the personal reports which you could always configure here, the new dashboard has shortcuts to important pages for managing your Check-ins, Jira account and more. Login to and see for yourself.
Troopr subscription can now be attached to Atlassian Billing. This allows customers to pay via their existing Atlassian payment profile. Troopr will sync the license in your linked Atlassian account when you choose to enable it.
- Troopr handles cases when the app is accessed from a Grid member workspace where it is not installed. More Grid workspace bugs resolved.
- Adding the user to an existing Troopr workspace in Grid now automatically replicate his Jira access. Removing the user removes his token from that workspace.
- The billing module now handles payment failures with support for self-service resolution options.
- Slack app dashboard (app home) now shows the last refresh time.
- Workspace picker now shows full name.
- You can now delete the Channel defaults configuration if you have permission
Workspace administration and a few more premium features were launched as part of the "Premium" plan. Learn more about the new pricing options.
Customers can now manage their Billing profile in the Troopr customer billing portal. The new portal will allow customers to
- Update payment method
- Download Invoices
- Change Troopr subscription plan
- Update Billing profile information
- Only workspace administrators will have access to the customer Billing portal. Read more about it.
- Fixed issue with showing default reporter value in the ticket creation form.
- Fixed issues with setting the default project tracker for the workspace.
- When a Slack message is converted to an issue with the "Task It" action, Troopr will use the sender of the Slack message as the reporter of the ticket.
- Admin access control enabled for Jira user mapping feature.
The person who installed Troopr is the Troopr workspace administrator by default. Now you can add more administrators using the Troopr workspace administration feature. Add any member of the workspace as administrator.
Configure Channel administrators and restrict access to channel configuration. For example, if you integrate with Jira Service Desk projects, you can set up the agents as channels administrators for the IT helpdesk channel, so customers reporting issues in the channel will be restricted.
- Dismiss button now made available in most of Troopr's messages.
- "Show Activity" message design is now consistent with typical notification design.
- Jira grouped notifications now show the most recent update on top.