Most CRM systems contain plenty of useful information: leads, companies, contacts, deals, activities, and products. But collecting data and using it to make better decisions are different things. A BDR needs to know which leads need attention; a sales representative needs to prioritize deals; a sales manager needs to understand pipeline health; and an account manager needs visibility into the customer portfolio.
The same CRM data can serve all four roles — provided each team can build a view around its own questions. Here are four practical examples using custom dashboards built in Mria CRM for Jira.
Use Case 1: Lead Management Dashboard in Jira for BDR and SDR Teams
The challenge: Generating leads is only the first step. Teams also need to assign, qualify, and follow up with them consistently. Without a clear overview, new inquiries can sit untouched while attention goes to more visible opportunities.
Key Lead Management Metrics and CRM Widgets
- KPI Cards: New Leads, Open Leads, Conversion Rate, and Unassigned Leads.
- Leads by Status: where leads are accumulating across stages such as New, Pending, Contacted, Follow-up, and Qualified.
- Leads by Source: the mix of acquisition channels, including paid ads, email campaigns, social media, events, and referrals.
- Stale Records: specific leads with old or no recorded activity, including their status, last activity, and assignee.
For example, the dashboard shown below surfaces 100 open leads, a 29% conversion rate, and one unassigned lead. Its status chart highlights 32 leads in New and 22 in Pending, while the stale-record list points to individual records needing review. The source chart shows how incoming leads are distributed across channels — useful context for deciding where to investigate further.
Example 1. BDR | Lead Management & Qualification dashboard in Jira.
The decision: Which leads should be assigned or contacted today, and where is qualification slowing down? Rather than opening individual records to discover the problem, a BDR can begin with the exceptions and work from there.
Use Case 2: Sales Pipeline Dashboard in Jira for Sales Representatives
The challenge: A rep may own many deals at different stages, but not all deserve equal attention. Some are close to an expected closing date; others have gone quiet. A total pipeline figure alone cannot tell a rep what to do next.
Sales Pipeline Metrics, Forecasts, and Follow-Ups
- KPI Cards: Open Deals, Pipeline Value, Deals Won, and Revenue Won.
- Pipeline Funnel: deal counts at each stage, from New and Discovery through Negotiation and Proposal to outcomes.
- Pipeline Value Funnel: monetary value distributed across pipeline stages, with value and weighted-value views.
- Forecast by Closing Month: open deal amounts grouped by expected closing month, including deals with no closing date.
- Deals Closing Soon: the actual opportunities approaching their closing dates.
- Stale Records: open deals with no recent activity, including last activity and owner.
In the example, the dashboard displays 31 open deals and a pipeline value of 350K. The forecast includes a substantial “No closing date” category. That is an operational signal: a rep may need to review expected close dates before relying on the forecast. The Deals Closing Soon and Stale Records lists then translate that overview into concrete follow-up work.
Example 2. Sales representative dashboard in Jira: pipeline stages, closing forecast, and deal follow-ups.
The decision: Which opportunities should I contact, advance, or update this week? The dashboard connects the bigger pipeline picture with the individual records that require action.
Use Case 3: Sales Management Dashboard in Jira for Pipeline and Team Performance
The challenge: A healthy-looking pipeline does not necessarily mean predictable revenue. Leaders need to know who owns the opportunities, where value is concentrated, when deals might close, how long sales cycles take, and why deals are lost.
Sales Forecasting, Team Performance, and Pipeline Health Metrics
- KPI Cards: Pipeline Value, Weighted Pipeline Value, Deals Won, Deals Lost, Revenue Won, and Sales Cycle Length.
- Deals by Assignee: comparison of deal value across sales owners.
- Pipeline by Stage: the distribution of open pipeline value by stage.
- Forecast by Closing Month: expected deal amounts by month, including records without a closing date.
- Loss Reasons: the stated reasons behind lost deals.
- Deals Closing Soon and Stale Records: deal-level lists for immediate management follow-up.
The example shows 308K in pipeline value versus 187K in weighted pipeline value — a reminder that headline pipeline and probability-adjusted pipeline are not the same. It also shows a sales cycle length of 111 and a breakdown of loss reasons, with product fit appearing more often than the other recorded reasons. These signals can guide deal reviews and discussions with the product team, but they should be interpreted in context, especially when the number of lost deals with a recorded reason is small.
Example 3. Sales manager dashboard in Jira: weighted pipeline, team distribution, forecast, and loss analysis.
The decision: Is the pipeline sufficiently mature? Are expected closing dates realistic? Which deals need coaching or intervention? Are repeated loss reasons suggesting a product, positioning, or qualification issue?
Use Case 4: Account Management Dashboard in Jira for Customer Portfolio Analytics
The challenge: Once a prospect becomes a customer, teams need a company-level view rather than a deal-only perspective. Account managers want to understand the size and composition of their portfolio and identify accounts with active commercial opportunities.
Customer Segmentation and Company Pipeline Insights
- KPI Cards: Total Contacts, Total Companies, New Companies, and New Contacts.
- Companies by Type: a breakdown of Customers, Resellers, Partners, and other configured company categories.
- Top Companies by Pipeline: a ranked list of companies with open deal counts and pipeline values.
In the example, the dashboard shows 98 companies and 98 contacts, with 7 new companies and 13 new contacts in the selected period. Companies by Type reveals a portfolio heavily weighted toward customers (91), alongside resellers and partners. The Top Companies by Pipeline list makes it easy to see which organizations currently have the largest open opportunities.
Example 4. Account Management | Customer Portfolio dashboard in Jira.
The decision: How is the company and contact base evolving? What kinds of organizations are in the portfolio? Which accounts deserve a closer commercial review? The dashboard does not itself measure retention or customer health; it offers a practical starting point for account prioritization and portfolio analysis.
Why Custom CRM Dashboards Matter for Teams Working in Jira
For teams already using Jira for delivery, product work, and support, commercial context becomes more useful when it is available alongside the work those teams manage. Mria CRM for Jira brings leads, deals, contacts, and companies into the Atlassian environment. Role-specific CRM dashboards help sales and customer-facing teams interpret that information without forcing every role into the same reporting view.
This also creates opportunities to connect commercial questions with operational workflows. A team can review a customer’s commercial opportunities and then explore related delivery or support context in Jira. Dashboards visualize CRM metrics; they are not a replacement for Jira issue analysis or JQL-based investigation.
See It in Action: How to Create Custom CRM Dashboards in Jira
Want to see how it works in practice? In this short video, we walk through how to create and customize dashboards in Mria CRM, select reporting widgets, and build a dashboard around your team's needs.
CRM Dashboards vs. Custom Reports: Visual Insights and Detailed Analysis
Dashboards in Mria CRM are designed to visualize CRM data and provide at-a-glance insights into the metrics that matter most to each team. But a high-level overview is not always enough.
Mria CRM also has a dedicated Reports section, where users can create custom reports to explore CRM records in more detail. While dashboards help teams quickly understand what is happening, custom reports help them examine the underlying data and answer more specific questions. The Report Snapshot widget can also surface the first rows of a saved report directly on a dashboard, with a link to open the full report.
In short: dashboards help you see the bigger picture; reports help you explore the details behind it.
Turn CRM Reporting in Jira into Better Sales and Customer Decisions
The goal of custom reporting is not to display as many charts as possible. It is to give each team the right information for the decisions they make: lead assignment and qualification for BDRs; deal prioritization for reps; forecasting and coaching for sales managers; and portfolio visibility for account managers.
These four dashboards use the same CRM, but tell four different stories. That is the value of flexible, role-based reporting: teams can spend less time assembling information and more time acting on it.
How does your team approach CRM reporting in Jira? Do you prefer a single shared dashboard or different views for sales, account management, and leadership? I would love to hear how other Atlassian teams work with customer and sales insights.
Explore Mria CRM for Jira: https://marketplace.atlassian.com/apps/4108768729/mria-crm?hosting=cloud&tab=overview
