You Can Now Evaluate a Jira-Native CRM in Just One Day

[#1]

Search for CRM in Jira, and you will still find advice about adapting sales templates or recreating Leads, Deals, Contacts, and Companies with custom Jira issue types. That means building and maintaining a CRM from Jira work items instead of using a system designed for customer and sales management. CRM in Jira has already moved beyond improvised sales tracking.

Mria CRM changes what CRM in Jira can be. Leads, Contacts, Companies, Deals, and Products exist as separate, purpose-built CRM entities rather than custom Jira issue types. Each has its own records, fields, lists, filters, and relationships with other entities. A Lead can be qualified and converted into a Deal; a Deal can connect the relevant Contact, Company, and Products; and Tasks, Meetings, and Notes preserve the activity history around the Lead or Deal. This connected structure powers sales pipelines, probabilities, Dashboard metrics, and Reports. CRM records can also be linked directly with Jira work items, boards, and Confluence spaces.

Until now, understanding how all these capabilities work together still required reading documentation, booking a demonstration, or manually preparing an empty trial.

Now, when you install Mria CRM, it already contains connected sample records so you can immediately test Leads, Deals, Contacts, Companies, pipelines, activities, reports, settings, and Jira, JSM, and Confluence connections, giving you everything you need to evaluate a working Jira-native CRM in one day.

Start with a working CRM in Jira, not an empty workspace

When Mria CRM is installed on a Jira site for the first time, the workspace includes a small set of sample records across:

• Leads
• Deals
• Contacts
• Companies
• Products

Every sample record has the [SAMPLE] suffix, making it easy to distinguish from data created by your team.

The records demonstrate the CRM data model in practice. Sample Deals reference sample Contacts, Companies, and Products, so you can follow the relationships between them and understand how customer information is organized. Sample Leads allow you to explore early-stage sales work, move records through the Lead pipeline, and convert a qualified Lead into a Deal. 

The sample data also gives you immediate access to meaningful pipeline funnels, activity metrics, and other results on the Dashboard and in Reports.

How to Evaluate CRM in Jira in One Day?

The sample data gives you a ready starting point for testing the main Mria CRM workflows.

You can review the existing records, change them, create your own, and follow a customer journey from Lead qualification to a Won or Lost Deal.

• Explore the CRM structure

Start by examining how Mria CRM separates different types of sales and customer data. Leads represent potential customers before qualification. Contacts represent individual people, Companies represent the organizations they belong to, Deals represent active sales opportunities, and Products represent what the team is selling.

Use the sample records to compare how information is organized across these entities. Lead-specific information remains with the Lead, customer details are stored in Contacts and Companies, opportunity data belongs to Deals, and Products can be associated with the relevant sales records.

The structure also prevents customer information from being confined to a single sales opportunity. The same Contact or Company can remain part of the CRM beyond one Deal, while each Deal keeps its own value, stage, probability, products, and other opportunity-specific data.

By opening the sample records and moving between related entities, you can understand where different types of information belong and how they form a structured CRM data model.

• Test CRM views, filters, and search

Leads, Deals, Contacts, Companies, and Products each have their own list where teams can search, review, and manage records. Sample data makes these lists ready to test immediately.

You can choose which standard or custom fields appear as columns and apply filters to focus on the records relevant to a particular task. For example, you can filter Leads by status or source, or narrow Deals by owner or pipeline stage. Different values in the sample records make the effect of each filter immediately visible.

Leads and Deals are available in both Table and Kanban views. Table view is useful for comparing detailed record data, while Kanban organizes Leads by status and Deals by pipeline stage. Switching between them shows how the same CRM data supports detailed list management and visual pipeline work.

• Review Lead and Deal pipelines

Open the Lead and Deal Kanban boards to see how records are organized by Lead status or Deal stage.

Move sample records between columns, inspect their details, and review how a team can manage progress through the sales process.

In the Deal pipeline, you can also examine the probability assigned to each stage and see the weighted Deal amount directly on the board.

Mria CRM supports multiple Deal pipelines, allowing teams to use different sales processes for different services, products, markets, or types of opportunity. You can switch between pipelines directly from the Deal board and review the Deals and stages associated with each one.

• Convert a Lead into a Deal

Choose one of the sample Leads and take it through a realistic qualification process. Update its status, assign it to a team member, add relevant Products, and record the work completed during qualification.

Before converting the Lead, make sure it has a linked Contact and Company. You can create new Contact and Company records or link existing ones, but the selected Contact must be associated with the selected Company so that the Lead has a valid Contact–Company pair.

Once the Lead is qualified and the customer records are connected, convert it into a Deal. You can then continue managing the opportunity with the Contact, Company, Products, and relevant Lead context linked to the resulting Deal.

This allows you to test how Mria CRM moves a potential customer into the active sales pipeline while preserving a structured relationship between the Lead, Contact, Company, and Deal.

• Connect CRM records with Jira, Jira Service Management, and Confluence

Mria CRM connects customer information with delivery, product, support, and documentation work across the Atlassian environment.

You can link Jira work items, boards and spaces, JSM tickets and Confluencepages and spaces to:

• Leads
• Deals
• Contacts
• Companies
• Products

To test this, choose one of the sample Deals and link it to a Jira work item (issue, board or space). Then open the linked work item and review the Mria CRM panel available directly inside the issue. The panel shows the related CRM records, allowing delivery, product, or other Jira users to access the relevant Deal and customer context without leaving Jira.

You can also test the Jira Service Management integration by opening a service request and checking the Mria CRM panel. Mria CRM automatically checks whether the requester already exists in the CRM. If no matching customer is found, the panel offers to create a Contact or both a Contact and Lead in one click.

Finally, link a Confluence space to a sample CRM record to see how customer documentation can remain accessible from the relevant Lead, Deal, Contact, Company, or Product.

Together, these connections show how CRM data can follow the customer across sales, delivery, support, and documentation instead of remaining isolated from the work managed in Jira, JSM, and Confluence.

• Create Tasks, Meetings, and Notes

On a Lead or Deal, you can create Tasks, schedule Meetings, add Notes, assign Tasks or Meetings to team members, and review the activity history associated with the record.

For example, add Notes from a discovery call, create a follow-up Task, and schedule the next Meeting for a sample Deal. This keeps completed interactions and planned next steps connected with the relevant Lead or Deal.

Then open the Activities module to see how assigned CRM and Jira work is organized into four sections:

• Assigned to Me shows Jira work items assigned to you and linked to CRM records.
• My CRM Activities shows Tasks and Meetings created inside Leads or Deals. It can be filtered by activity type.
• My Leads shows Leads assigned to you, including their creation date and status.
• My Deals shows your active Deals with their value, closing date, and pipeline stage.

Each section supports sorting, and you can open a Lead, Deal, or linked Jira work item directly from the Activities module. This makes the module useful as a daily view of the CRM and Jira work currently assigned to you.

• Move a Deal through the pipeline

Continue working with the Deal created from your sample Lead.

Move it through different pipeline stages and see how the probability assigned to each stage affects the weighted Deal amount.

You can then mark the Deal as Won or Lost to complete the sales workflow and review how the outcome is reflected in the CRM metrics.

• Review the Dashboard and Reports

The sample records provide enough data to review the Mria CRM Dashboard and Reports immediately after installation.

The Dashboard shows the overall sales picture through key metrics, pipeline funnels, pipeline value, conversion results, and revenue trends. Reports provide more detailed views of the CRM records behind specific results, such as sales performance, open and lost Deals, pipeline stages, and Products.

After converting a Lead, moving a Deal through the pipeline, or marking it as Won or Lost, return to the Dashboard and Reports to see how those changes affect both the summary metrics and the underlying sales data.

• Adapt the CRM to your sales process

Open Mria CRM Settings to evaluate how the CRM can be adapted to the way your team works.

You can:

• Create custom fields for Leads, Deals, Contacts, Companies, and Products
• Add, edit, reorder, or remove Lead sources
• Add, edit, reorder, or remove Lead statuses
• Create or edit multiple Deal pipelines
• Add, remove, rename, and reorder pipeline stages
• Set a probability for each Deal stage
• Choose colours for Lead statuses and Deal stages
• Configure tags for Leads, Deals, Contacts, and Companies
• Set the workspace currency
• Review roles and permissions
• Import and export CRM data

For example, create a pipeline for a particular service or sales process, define its stages and probabilities, choose the stage colours, and move a sample Deal through the new workflow. You can also create a custom field for one of the CRM entities, add a value to a sample record, and see how the field appears in record details, lists, filters, and exports.

Move from sample data to your own CRM records

Once you have finished evaluating Mria CRM, you can remove the sample records and start working with your own data. All sample records include the [SAMPLE] suffix, so they are easy to identify.

Follow the Installation Guide for the correct deletion sequence. You can then finalize your CRM settings and import or create your own Leads, Contacts, Companies, Products, and Deals.

➡️ Read the Installation Guide: https://mriacorp.atlassian.net/wiki/spaces/MC/pages/123568308/Installation+Guide#%F0%9F%A7%AA-Sample-Data-on-New-Installations 

Evaluate CRM in Jira through a working product

Understanding the possibilities of CRM in Jira should not require weeks of research, comparisons across product pages, or several introductory meetings. Anyone who still doubts whether Jira can support a capable, purpose-built CRM can now test it directly and see the answer for themselves in a single day.

Install Mria CRM, use the sample data to follow a realistic sales workflow, and evaluate the CRM directly.

By the end of the day, you can understand:

• How the CRM data model represents your customers and sales process
• How Leads become Deals
• How activities and customer history are managed
• How pipelines, probabilities, Reports, and Dashboard metrics work
• How CRM records connect with Jira and Confluence
• How the CRM can be configured for your team

You can now evaluate a Jira-native CRM through practical use and decide whether it fits your team based on the product itself.

➡️ Try Mria CRM on the Atlassian Marketplace: https://marketplace.atlassian.com/apps/4108768729/mria-crm?hosting=cloud