Anton Storozhuk _Mria Labs_ Atlassian Partner

Today, we are introducing the Mria CRM REST API, giving customers and partners programmatic access to CRM data and workflows managed inside Jira. The API currently provides 190 operations across Leads, Contacts, Companies, Deals, Products, Activities, relationships, custom fields, Jira and Confluence links, and sales…

Imagine your team releases a feature in Jira that 20 potential customers have been waiting for. How many of those people will actually hear from Sales? Or consider the Leads that haven't been contacted in weeks, the Deals approaching their closing dates, and the customer requests that need input from several departments.…

Permissions in a traditional external CRM are usually built around the sales organization. Sales representatives, managers, and administrators receive different levels of access within a system used primarily by sales. CRM in Jira requires a broader permissions model. Customer-related work already extends across teams in…

Jira tracks the work. Confluence captures knowledge and decisions. Jira Service Management and Customer Service Management handle customer requests. Mria CRM connects all of it to the customer relationship, making CRM part of Atlassian’s System of Work. A customer relationship never fits inside one CRM record. It continues…

Complex B2B sales bring many people, organizations, decisions, and workstreams into the same opportunity. An enterprise Deal may involve an end customer and reseller, a parent company and signing subsidiary, an implementation partner, and a buying group spanning business, technical, procurement, legal, security, and…

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…

Customer relationships do not live in project boards. They live in conversations: emails, follow-ups, replies, threads that go back months. For years, Jira teams have had to accept that this part of the customer relationship would always exist somewhere else. Mria CRM was built to change that. It is a native CRM for Jira,…

When Rovo became available in Jira, the most obvious use cases were easy to spot. Search, summarization, quick answers, and navigation through information. Those directions made sense, and they immediately showed why Atlassian was investing in this layer. But for us, the more interesting question was different. What…

Most teams manage customer and sales data in a separate CRM, while Jira is used for execution. This separation creates constant friction. A deal may look active in the CRM, but its real state depends on what is happening in Jira projects, support queues, and documentation. To understand that state, teams often have to…

In Mria CRM, pipelines are an explicit CRM structure that defines how deals move through stages, how progress is reviewed, and how sales data is interpreted inside Jira. Mria CRM supports both pipeline customization (stages, order, colors, probability) and multiple pipelines because a single, fixed pipeline stops being…

Teams that run sales through Mria CRM: CRM for Jira Teams usually do so to keep sales work in the same system as delivery, support, and internal collaboration. Leads, deals, and activities are managed as part of Jira’s daily workflow, with clear ownership, shared visibility, and traceability. Once that structure is in…

“Import customers into Jira” sounds like a single task. In the Atlassian ecosystem, it is not. What you can import, what gets created, and where that data is usable depends on which product actually owns the customer model in your site. Atlassian currently spreads “customer” concepts across three layers: Jira Core (Jira…

As more teams move customer operations into Jira Cloud, the expectations for Marketplace apps in sensitive categories like CRM have increased significantly. Reliability, operational clarity, and architectural transparency now shape the evaluation process as much as features do. With that in mind, we are pleased to share…

Hi Community! Many teams rely on Confluence to capture the kind of information that doesn’t fit neatly into Jira issues - customer insights from discovery calls, internal discussions about scope, onboarding materials, planning notes, requirement drafts, and summaries from cross-functional meetings. This content drives…

Managing customer information across multiple tools is still the reality for many Jira teams - spreadsheets for contacts, old or disconnected CRMs for historical records, event lists for leads, shared drives for partner details, and support tickets sitting elsewhere. The result is predictable: scattered context,…

We’ve shipped one of the most requested and impactful improvements to Mria CRM: CRM for Jira Teams - a fully featured Contacts Import system that brings real CRM-grade data management into Jira. Contacts Import is a major step forward for teams moving customer operations into Jira. It gives you a fast, structured, and…

Lead management is the connective tissue between marketing activity and predictable revenue. It is where potential demand becomes structured opportunity and where modern B2B companies either build a reliable revenue engine or quietly lose momentum through delays, scattered information, and unstructured qualification. When…

We’ve just released a new version of Mria CRM: CRM for Jira Teams - the first truly native CRM built on Atlassian Forge - introducing three updates that make working with customer data inside Jira faster, clearer, and more connected. Now you can import leads at scale, stay on top of every update instantly, and record…

If you’ve ever tried managing deals, contacts, or accounts in Jira, you’re not alone. Most teams try it at some point. Sometimes, because there’s no CRM in place. Sometimes, because Jira is already the center of everything else. It’s a fair idea. Jira already handles your delivery, support, and internal processes. So why…

Mria CRM has now been live on the Atlassian Marketplace for just over a month. In that short time, we’ve already seen how different teams are putting it to use, not only in sales, but across customer success, product, finance, and support. The common thread is simple: by linking Leads, Deals, Contacts, and Companies…

We’ve just shipped an update in Mria CRM: CRM for Jira Teams, and it’s all about one thing: making Jira and the company's daily work more connected to customers. If you’ve ever wondered “What should I focus on today?” or “Which customer is this task for?” — this release is designed to answer those questions inside Jira. A…

We’re excited to share that Mria CRM for Jira is now live on the Atlassian Marketplace. Developed by Mria Labs Inc. and built on Forge, Mria CRM introduces a new approach to customer management inside Jira. Instead of customizing issue types or stretching dashboards to fit CRM needs or relying on heavy external CRMs with…

You may discuss "Smart Git Integration for Jira" app here.