Share Custom Jira Reports in Slack
The quickest way to share a Jira report with your team is to share in your team’s Slack channel. This allows for everyone to discuss the report right there when necessary but it comes with many other benefits as well.
Benefits of sharing Jira Reports in Slack
Reports are easily accessible, people do not have to go to Jira and look for it
Team can react/discuss the report right there in Slack
The only way to share Jira reports currently is by copying the relevant link to the report and sharing it manually in Slack channel. This is not ideal and has limited value as well.
This is where Troopr comes into the picture. Troopr Reports for Jira allows users to set up automated reporting from Jira projects into Slack channels. Troopr actually constructs the entire report based on the user’s needs and delivers them to Slack as beautiful charts and lists that are actionable with drill down capabilities.
Benefits of using Troopr Reports
Troopr goes beyond link sharing to share the actual report to the Slack channels. Benefits of using Troopr Reports for Jira include
Easy 3 step configuration for any Troopr report
Reports are not links to Jira pages, but actual charts and lists in Slack
Choose from 20+ report templates or setup a fully custom one
Everyone including people who don’t access Jira can see the reports in Slack
Drill through the report for more insights directly in Slack
Take action on the report issues directly in Slack (when you have relevant permissions)
Making a custom Report
When the pre-built templates don't fit your team’s needs, build a completely custom one. Troopr allows you to configure a custom report by specifying any JQL in the report configuration.
Let's look at how we can go about building a custom JQL report using Troopr reports. The configuration involves 3 easy steps.
Step 1: Configure the JQL
Choose Custom JQL template and enter JQL value
Step 2: Configure the schedule
Set up time schedule to receive report in Slack
Step 3: Configure the delivery options
Choose where you want to receive the report in Slack
Post setup actions
Once the report is set up, the report can be tested to see if it is working as expected. To do this you can find your report in the list and choose the “Run Now” option. This will send the report to the configured channel (if there is any data to send).
Keep the team in the loop
The moment the report is setup, a notification is sent to the relevant channel that the report owner (person who set up the report) has setup the report to be delivered at set frequency in the channel. This keeps the team informed so they are not taken by surprise when it actually happens. Also every report has a footer at the bottom of the report with information about the report and the person who set it up. So if anyone has reservations about the reporting they know who to reach out to.
Keep your Jira admin in the loop
Technically Troopr has no limitation on the number of reports that you can set up. Troopr’s implementation of reporting is heavily optimized for performance and resource utilization, however you may do well to keep your Jira administrator in the loop about the reports you intend to set up. Also the Troopr subscription plans your organization uses may have some limitations on usage.
Access control privileges
Anyone in the team can see the reports setup by their team members. However only the report owner or workspace administrator can edit/delete the report. When the administrator finds a problem with a report setup by a member of the team, they can discuss it with them or when necessary immediately disable or delete the report.
What are the other reports I can use?
Troopr’s Jira bot for Slack comes with 20+ report templates including
Sprint burndown chart: Gives the team a visual representation of the amount of work that has been completed and work remaining in a Sprint.
Sprint velocity chart: Gives a visual representation of the amount of value delivered in each Sprint, enabling the team to predict the amount of work that can be done in the future Sprints.
Workload pie chart: Gives the team a visual representation of all the issues in a specific project board by user or other attributes.
Issues by type: Shows all issues in a specific project board by issue type.
Issues by Status: Shows all issues in a specific project board by issues status.
Issues by Assignee: Shows all issues in a specific project board by Assignee.
Issues by Priority: Shows all issues in a specific project board by issue priority.
Issues missing updates: Shows all issues in a specific project board that are missing updates for configured ‘x’ days.
Issues missing estimates: Shows all issues in a specific project board that are missing task estimates.
Estimates too high in Sprint: Shows all issues in a specific project board with estimates higher than the specified value in the active Sprint.
Troopr Slack integration for Jira is available for install from Atlassian Marketplace and Slack App Directory. You can pick from the already available report templates/build a unique one in a few clicks configured for team needs and workflow.