Atlassian for MSP?

QMSpot _ Patrick Gehlich

Hello together,
I did some research in the community and internet. But i didn´t found much infos.

I also created another thread here, few days before, regarding multiple Support Spaces, Pipelines and External Customer Support.

now i can shorten my question:
Is Atlassian Suitable for MSP Ticketing and ITSM?

I cannot even create a Customer/Contact without creating Extra fields.
https://support.atlassian.com/jira-service-management-cloud/docs/manage-customer-detail-fields/

This article says, that this features are moved to CSM.
But CSM compared to JSM feels incomplete.
My technicians need to be able to create a Customer on the fly, when he is on the phone.

I need a honest answer please, because next week i need to pitch it to my CTO.
I personally need Jira for Project Management. It´s the best for my case.
But we also need a Ticket System and Support Platform for external customers.

I also don´t think, that i get the Budget for both Systems: Jira + External Ticket system.

Thanks a lot

Arkadiusz Wroblewski

Hello and Welcome @QMSpot _ Patrick Gehlich 

To be Honest....

JSM works well for external customer ticketing and ITSM. Agents can raise tickets on behalf of customers, customers can use the portal, email, or be added directly by agents. It's a solid foundation.

However, you've correctly identified the main gap: JSM is not a CRM. The customer/contact management features are basic, and the richer functionality has been moved toward CSM (Customer Service Management), which is a newer product that's still maturing. If your technicians need to create and manage contacts on the fly with meaningful context (company, site, SLA tier, etc.) that's where JSM starts to feel incomplete for a true MSP workflow.

The other MSP-specific challenge is client isolation. If you support multiple companies, keeping their data, assets, and tickets properly separated in a single JSM instance requires significant configuration effort and is not straightforward out of the box.

So my honest take: Jira for project management is a strong call. JSM for external ticketing is workable, but if your MSP workflows rely heavily on contact management and multi-tenant isolation, you'll be working around limitations rather than with native features. It's worth being upfront about that with your CTO rather than discovering it post-implementation.