Release Notes

Settings — Custom roles

• The three built-in roles are no longer the only option. Settings → Roles & Permissions now has + Create role, so you can build a role that matches how your team actually works.

• Each role gets a permission matrix: View / Create / Edit / Delete across the CRM modules and the settings areas, plus a separate Reports toggle.

• Duplicate an existing role to start from something close rather than from nothing, and manage each role's Users and Groups from the same dialog.

• Administrator, User and Viewer stay as they are and cannot be deleted.

• See Roles & Permissions.

Contacts & Companies — Meetings, Tasks and Timeline

• Contacts and Companies gained Meetings and Tasks tabs, so work can be scheduled against the account or the person it belongs to rather than only against a Lead or Deal.

• Both also gained a Timeline, which records what happens to the record over time — the same history Leads and Deals already had.

• Meetings and Tasks created here show up in Activities alongside everything else.

• See Contacts and Companies.

Jira — custom field values kept in sync

• The Mria CRM custom fields on Jira work items now keep their values in step with the CRM, so a query like "Mria CRM Deals.Stage" = "Negotiation" reflects where the Deal actually is.

• See Mria CRM Custom Fields in Jira.

Fixes

• Deals Import — a probability written as 0.20 no longer fails the import. Decimal fractions and whole percentages are both accepted: 0.2 and 20 each store as 20%. See Deals Import.

• Activities — a Jira work item linked to a Product and assigned to you now appears under Assigned to me, as it already did for the other entities.

• Emails — fixed a query that could exceed its memory limit and leave a record showing no synced emails even though the mailbox had synced.

• Security and dependency updates.

Jira — Mria CRM custom fields

• Added five read-only custom fields to Jira work items: Mria CRM Leads, Mria CRM Deals, Mria CRM Contacts, Mria CRM Companies and Mria CRM Products. Each one lists the CRM records linked to that work item.

• The fields are available in JQL and in Jira automation, so you can filter and build rules on CRM data — for example "Mria CRM Leads.Assignee" = currentUser().

• See Mria CRM Custom Fields in Jira for every queryable parameter and the automation recipes.

• Requires the new permissions to be approved.

Teamwork Graph support

• Mria CRM records are now published to the Atlassian Teamwork Graph, the shared index behind Atlassian search and Rovo, so CRM records can surface alongside your Jira and Confluence content.

• Deals map to the graph's Deal type and Companies to Customer organization; Leads, Contacts and Products map to Work item. Records keep their Mria CRM permissions, and the graph syncs on Atlassian's own schedule rather than instantly.

• Requires the new permissions to be approved.

• See Teamwork Graph & Atlassian Search.

Rovo Studio — Mria CRM tools

• Mria CRM now appears in Rovo Studio under Connected apps, contributing three tools you can attach to an agent you build yourself: Create lead, Search leads and Update lead.

• This is separate from the ready-made Mria CRM Assistant — these are the individual actions, for your own agents. More tools will follow.

• See Mria CRM in Rovo Studio. These are Atlassian's tools that Mria CRM plugs into — there is no Mria CRM MCP server.

Leads — Import options

• Lead Import gained Link to existing Contacts / Companies and Create new Contacts / Companies from Lead info checkboxes, matching the options Contacts Import already had.

• Leads are matched by email. Unlike Contacts, Leads do not need unique emails, so several Leads can link to one Contact.

• Companies connect to Leads through Contacts, so a new or existing Contact is used to link them. A Company name that matches more than one Company is skipped.

• See Leads Import.

Lead to Deal conversion — better defaults

• Transfer activities from Lead to Deal and Transfer links are now selected by default in the Convert Lead dialog. They used to be off, and there was no way to fix a conversion once you had forgotten them.

• Clear either box to convert without carrying that data over.

• See Lead to Deal Conversion.

Gmail & Outlook — historical emails

• Connector admins can now import mail that predates the connection. Settings → Global Settings → Syncing emails → Sync emails from takes a date; everything received or sent on or after it (UTC) is imported.

• Site-wide — it applies to every connected mailbox — and it reaches back one year at most. Clearing the date stops further import but keeps what was already brought in.

• See Gmail Integration §1.8 and Outlook Integration §1.8.

Fixes & maintenance

• Import Completed no longer renders a stray 0 above the Records added row when every row in the file is skipped as a duplicate.

• Fixed a failing deal-suggestions query behind the Jira Service Management work item panel.

• Security and dependency updates across Mria CRM and Mria Contacts.

Deals — Bulk import

• Introduced Import Deals from .CSV / .XLSX files, completing bulk import across every entity — Leads, Contacts, Companies, Products and now Deals.

• Same five-step wizard as the other imports: Upload File → Map Fields → Map Values → Review Details → Import File.

• Deal imports and exports get their own Deals tab in Data Administration.

• See Deals Import for the full walkthrough.

Email — Attachments

• Added Attach files to the email composer on Contacts, Leads and Deals, so a message can carry documents as well as inline images.

• Accepted types: .pdf .doc .docx .xlsx .txt .csv .png .jpg .jpeg .gif .json .zip.

• See Gmail Integration and Outlook Integration.

Email Templates — HTML editor

• The template editor gained a Rich text / HTML toggle, so you can paste markup straight out of an email design tool instead of rebuilding the layout by hand.

• Pasted HTML is sanitised on save: <style> blocks, Outlook conditional comments and background images are removed, and images need https URLs.

• A live preview under the editor renders the template with sample data, so merge fields like {{company.name}} show as real values while you write.

• See Email Templates.

Email Templates — Delete starter templates

• The three starter templates that ship with Mria CRM can now be deleted from Settings → Email Templates, the same as any template you created yourself.

• See Email Templates.

All entities — Bulk field editing

• Added Edit fields to the bulk actions bar across Leads, Deals, Contacts, Companies, and Products. Select records in table view, then update them all in one pass — no more opening records one at a time to re-assign a territory or re-tier a segment.

• Every field starts at Keep as is, so only what you deliberately change is touched. Single-value fields also offer Clear to empty them across the selection.

• Multi-value fields (Tags, Products) let you choose how the change applies: Add new, Replace all, Find and remove, or Remove all.

• Editable fields per entity — Leads: Status, Source, Assignee, Tags, Products. Deals: Assignee, Deal type, Source, Pipeline stage, Tags. Contacts: Company, Tags, Products. Companies: Country, City, State, Company Size, Industry, Tags, Products. Products: Category, Unit Type, Tax Rate.

• Add links attaches the same Jira work item, Jira space, Jira board, Confluence page, or web link to every selected record.

Email Templates

• Introduced Email Templates — reusable emails you can insert from any Contact, Lead, or Deal. Managed under Settings → Email Templates, with no admin setup: any user can create one.

• Each template is Private (only you) or Public (anyone in the workspace can use it; only the owner can edit). Keep it Private while you refine the wording, then make it Public for the team.

• Merge fields — {{contact.name}}, {{company.name}}, {{deal.name}}, {{lead.name}}, and {{my.name}} — work in both the subject and the body.

• The composer's Template button opens a picker with a live preview filled in for the record you're on, so you see the real email before inserting it. + Save as template turns the draft you've just written into a reusable one.

• Every workspace ships with three Starter templates so the picker isn't empty on day one. Templates can be reordered per user, duplicated, and moved in and out via Import / Export.

Deals — Multiple Contacts & Companies

• A Deal can now be linked to several Contacts and several Companies, each panel with its own count and + Add action. One of each is marked Primary.

• This is what multi-party deals needed — a reseller alongside the end customer, a parent company and the subsidiary actually signing, or a procurement intermediary. Previously you picked one and recorded the rest in a note.

• The Deals table now shows Primary Company and Primary Contact columns; open the Deal for the full list.

Deals — Contacts and Companies now optional

• Creating a Deal no longer requires a Contact or a Company, and the Contact no longer has to belong to the Company first. Only Deal Name, Pipeline, and Pipeline stage are required.

• Useful when a deal lands before you know who you'll actually be dealing with — record the opportunity now, attach the people later.

Import — Failing rows named

• Validation errors now report the specific row numbers that failed, not just a count. On a file of thousands of rows, a single malformed value is otherwise nearly impossible to find — now you can jump straight to it, fix it, and re-upload.

• Applies to Leads, Contacts, Companies, and Products imports.

REST API — Extended lists

• List endpoints can return full record details instead of a trimmed summary, and records now carry their created and updated timestamps — which is what makes incremental syncing practical: pull only what changed since your last run. See REST API.

Bug Fixes

• Fixed the "No email address found for Lead" error.

All entities — Bulk delete

• Added bulk delete across Leads, Deals, Contacts, Companies, and Products. Select records with the row checkboxes in table view, then delete them in one action.

• The header checkbox selects every record on the current page. To go wider, use the Select all N link in the bulk actions bar, which extends the selection to everything matching your current filters.

• Records that can't be removed (for example a Contact still used on a Deal, or a Company with linked records) are skipped and the rest of the batch continues. One protected record no longer fails the whole operation.

• Bulk delete is permanent and cannot be undone — check the count in the bulk actions bar before confirming.

Leads & Deals — Files tab

• The Files tab is available again on Leads and Deals following an Atlassian platform fix. Upload contracts, proposals, and supporting documents straight onto a record — up to 1.5 MB per file. See Activities Breakdown.

Bug Fixes

• Fixed a Phone field corruption on export/import round-trips: exporting Leads to CSV and re-importing the same file added a leading apostrophe to phone numbers ('+44 4813 8074 instead of +44 4813 8074). The apostrophe the export adds to stop spreadsheets reformatting the number is now stripped on import.

REST API

• Introduced the Mria CRM REST API — read and write your CRM data from outside Jira, so you can sync with other systems, feed a data warehouse, or automate record creation from your own tooling.

• Documentation covers Setup and authentication, the OpenAPI specification, and worked examples for Node.js and Postman.

Leads & Deals — Files

• The Files tab is now generally available on Leads and Deals (previously early access). Maximum file size is 1.5 MB.

• The Files section stays collapsed while it isn't in use and expands on click, so records with attachments stay compact. See Activities Breakdown.

Companies — Notes / Files tabs

• Added a Notes / Files tab strip to the Company full view, bringing Company-level attachments in line with Leads and Deals.

• Contracts, NDAs, and other paperwork that belongs to the account rather than to one specific opportunity now live on the Company itself.

Contacts — Secondary email

• Contacts can now hold a second email address alongside the primary one — useful when the same person writes from both a work and a personal mailbox. It appears as Secondary Email in the Details panel and can be edited inline.

JSM Integration — Deal suggestions & CSM support

• When a Contact or Company is linked to a service desk ticket, the CRM panel now suggests that customer's three most recent Deals (by created date) along with the total number of Deals they have — so an agent sees the commercial context without leaving the ticket. Any suggested Deal can be linked in one click.

• Added support for Customer Service Management (CSM) tickets: matching now uses the Reporter's email rather than the Customer field, which on CSM tickets points at the organisation rather than the person who raised the request. See JSM Integration.

Email — Images & prefilled recipients

• Gmail and Outlook emails now support images in the message body, so signatures, screenshots, and inline graphics render properly instead of being dropped.

• The To field is pre-filled by default when composing from a Lead, Contact, or Deal.

• Fixed replying to HTML emails, which previously produced broken formatting.

Meetings — Custom time

• You can now type any start or end time when scheduling a Meeting instead of choosing from the preset slots — handy for calls that don't fall on a round interval, or for logging a past meeting at its real time. See Activities Breakdown.

Amount formatting

• The Amount column no longer forces a dollar sign — amounts follow the workspace currency set by your administrator, so teams working in GBP, EUR, and other currencies see the right symbol.

In-app feedback survey

• The in-app feedback link now points to an Atlassian-hosted survey form instead of the previous Google Form — one less third-party service in the loop. We still read every response.

Bug Fixes & Security

• Fixed an error when unlinking a converted Lead from a JSM ticket.

• Deleted or missing Leads, Deals, and other records now redirect to a proper 404 page instead of generating repeated errors.

• Fixed scheduled trigger errors in Mria Contacts.

• Optimised the app manifest to stay within Atlassian's Forge deployment limits — internal change, no user-facing impact.

• Resolved third-party dependency vulnerabilities flagged by Snyk.

Products — Bulk import

Introduced Products Import from .CSV / .XLSX files. Rounds out the import story — Leads, Contacts, Companies, and now Products can all be seeded in bulk. Duplicates are matched by Name, with Update existing and Skip duplicates options.

Leads Import — Products mapping

Extended Leads Import's Map Values step: if your file has a Products column, its values are matched to existing Products in your catalog and linked to each imported Lead. New Products cannot be created through Leads Import — add them first via Products Import.