Follow new features and improvements to Troopr Projects here.
Support for multi-issue unfurl - users can mention multiple Jira issue keys and all of them will unfurl in a compact list. The list can be expanded for more information or to take action.
For large teams that want to handle support requests from use of Troopr, you can now configure the email address or Slack channel where your customer feedback on Troopr will be sent.
If you are using Troopr Check-ins, you now have many more ways you can schedule your Check-ins with support for "Every 2 weeks", "Every 3 weeks", "Every 4 weeks", "First week of month", "Last week of month".
You can now type the following command to log time on any Jira issue in Slack./t log 1hr TP-121
If you use Troopr recurring Check-ins, your team can now look at team insights in one place for retrospective review. Drill down by date or team member to get more insightful reports.
If you are using Troopr's Retrospective Check-ins for your team, now you can let your participants vote and comments on the responses from other team members. Collaborate better with your team to continuously improve your team processes.
When a user verifies his Jira account in Trroopr, the verification profile is shared across all workspaces in the Slack grid, allowing the user to access Jira without verifying Jira account again in each workspace
Troopr user profiles in Slack grid are shared across workspaces in the grid, allowing Troopr to recognize external users taking action in an workspace.
Board configuration is now optional, so reports work at project level data. Reports also have support for JQL filter, so you can choose custom JQL filter option to set your own JQL filter for the report. Check out the new report templates for more.
Task-It and Comment-It have improved handling of attachments in the message now. User will be notified about the availability of media in the message and status of attaching it to the issue. "Comment-it" action now has Improved searching behaviour.
Now you can add custom questions alongside Jira issues that will be prompted for update during the Check-in.
Connect to Jira Server using OAuth 1.0. If you have used basic authentication for your existing connection, it will continue to work. You can delete the connection and use OAuth connection for your workspace if you choose. Read more about it here.
Performance improved across the board. Issue listing is now up to 4x faster. Reports are up to 10x faster. Significant performance enhancements across all actions for Jira Server and Cloud. For long running Jira actions, Troopr now indicates processing state until the action is complete. Hard limits are set for resource intensive reports and report creator is warned and notified about the breach of limits.
Now you can connect to any Jira Service Desk project just like you connect to a Jira Software project. All features of Troopr Slack integration for Jira work regardless of the project type including ticket creation, update, listing, notification, smart reports and nudges.
Now you can convert multiple Slack messages in a conversation to one Jira ticket by using the multi-message action feature. Pin the first message in the sequence with a emoji and perform the "Task It" or "Comment It" message action on the last message in the sequence. Now you have all the messages captured in one Jira ticket. Read more about it here.
List issues assigned to any user:1/t list @assigneeCopied!List issues by status:1/t list +status:<status>Copied!
The new upgraded issue creation form allows dynamic project and issue type selection. It auto populates all fields configured for creation in Jira and sorts the required fields to appear on top. It includes capabilities for assisted field value selections and validations. Creation form also respects status transition validation rules when configured. Issue edit form now allows editing any allowed field all in one form while complying to permissions and transition rules configured in Jira.
One simplified form to share issues in any Slack channel or to any person in Slack. Share action now supports ability to modify the content of the shared message
"Task it" and "Comment it" Slack message actions now support media attachments
You can use 2 new commands now for assign, update, comment & commands. This is in addition to existing commands for list, create, find and configure. See full list of commands hereAssign an issue to user1/t assign <issue-key> @userCopied!Display list of commands1/t commandsCopied!Update issue field with given value1/t update <issue-key> +<field>:<value>Copied!Add comment to an issue1/t comment <issue-key> <comment>Copied!
New Task Check-in template is now available. Task Check-in for Jira prompts participants to directly update the issues assigned to them during the Check-in time period and builds an aggregated report in the end. This way you get to see each person’s contribution while also keeping Jira updated. Read more about it here
Troopr Check-in template for Retrospective allows scrum teams to conduct retrospective meetings in Slack. You can setup a custom schedule, participants and customize the questions for the retrospective and have Troopr collect responses and prepare aggregate report for Slack and for the web. More about the feature here
Slack introduced recently a new way to access Slack apps called Shortcuts. Troopr Jira Slack integration now supports Shortcuts for Jira search and Jira issue listing.
In case you need to disable Jira unfurl, Troopr now allows you to disable unfurl when the issue key is part of Atlassian url in the Slack message.
Troopr now lets to convert Slack messages to a comment in an existing Jira issue in one click.
New issue creation modal allows users to select issue type during creation. Issue type, project and board auto-select to the channel defaults and also allow changes during creation. Switching issue types dynamically populates the creation form for the relevant issue type in the project.
Now you can click any attachment in Slack and attach that in one click to an existing Jira issue.
If you worry about Jira reports in Slack taking up too much real estate, Troopr now supports text summary reports that are compact and has all the data you need to track and take action.
Jira app customers can now more efficiently auto-map their team members Slack and Atlassian accounts. Troopr has more granular configuration to track and manage auto mapping.
Troopr Jira issue search now lets you find and act on issues faster in Slack. Also comes with option to search for multiple issues matching your search phrase.
If you are part of multiple Slack workspaces where Troopr is installed, you can now login once and switch workspaces with single click. This makes it easier to collaborate across teams while keeping separated access control.
You can now specify default Board (earlier you could only specify projects) for your issue listing and creation. Troopr will pull your issues from specified Board. New issues will also get created directly in the Board when possible. Boards are also supported in all your Jira Reports for Slack.
You can have your team members see issues assigned to them in Slack without the need to login and verify their Jira account. The verification process is delayed until the user needs to take action on issues.
Troopr will now auto-map Jira (Cloud) users with users in Slack when it detects profile matches with high confidence. For others, you can still manually map individually or on behalf of your team members.
Earlier you could type commands in Slack to get Jira issues, now you can see & update Jira issues assigned to you as soon as you visit Troopr app in Slack. No need for commands or buttons so your team to easily discover what Troopr can do for them. It also reduces friction even more for quickly creating and updating issues in Jira from Slack.This improvement required significant redesign to Troopr app functionality. We are committed to bringing more of Troopr to Slack Apphome and for the benefit more and more teams like yours.
Cleaner and improved UI in web application for current features. Easier navigation and use of mature UI components are highlights. Also makes way for some of the big new upgrades coming in May.