The Atlassian Service Collection, including the no longer available standalone Jira Service Management, is an integrated suite of service management applications built on Atlassian's unified Jira platform architecture. Designed to bring development, operations, internal IT, and external support teams onto a single workflow engine, the Service Collection consolidates support infrastructures to deliver service at high velocity.
$0
per month
DevRev
Score 8.4 out of 10
N/A
DevRev is a platform for SaaS and technology companies, helping back-office development match the rapid pace of front-office customer relationships. The vendor states its mission is to bring end users, support engineers, product managers, and developers together to create a company-wide culture of product and customer-centricity.
$9.99
per month per user
Pricing
Atlassian Service Collection, with Jira Service Management
DevRev
Editions & Modules
Free
$0
per month
Standard
$20
per agent/per month
Premium
$40
per agent/per month
Enterprise
Contact sales team
No answers on this topic
Offerings
Pricing Offerings
Atlassian Service Collection
DevRev
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
—
More Pricing Information
Community Pulse
Atlassian Service Collection, with Jira Service Management
DevRev
Features
Atlassian Service Collection, with Jira Service Management
DevRev
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Atlassian Service Collection, with Jira Service Management
8.9
86 Ratings
9% above category average
DevRev
-
Ratings
Organize and prioritize service tickets
9.385 Ratings
00 Ratings
Expert directory
9.02 Ratings
00 Ratings
Service restoration
9.52 Ratings
00 Ratings
Self-service tools
8.977 Ratings
00 Ratings
Subscription-based notifications
10.01 Ratings
00 Ratings
ITSM collaboration and documentation
8.472 Ratings
00 Ratings
ITSM reports and dashboards
7.573 Ratings
00 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
Atlassian Service Collection, with Jira Service Management
10.0
1 Ratings
20% above category average
DevRev
-
Ratings
Configuration mangement
10.01 Ratings
00 Ratings
Asset management dashboard
10.01 Ratings
00 Ratings
Policy and contract enforcement
10.01 Ratings
00 Ratings
Change management
Comparison of Change management features of Product A and Product B
Atlassian Service Collection, with Jira Service Management
7.9
80 Ratings
8% below category average
DevRev
-
Ratings
Change requests repository
8.873 Ratings
00 Ratings
Change calendar
6.52 Ratings
00 Ratings
Service-level management
8.478 Ratings
00 Ratings
Best Alternatives
Atlassian Service Collection, with Jira Service Management
Atlassian Service Collection, with Jira Service Management
DevRev
Likelihood to Recommend
Atlassian
I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.
DevRev is well suited for both multi-team and single-team environments, and teams can realize meaningful value even without having product, engineering, and support all onboarded at the same time. Its strength is clearest when used by customer-facing and delivery-adjacent teams that benefit from shared context and tighter feedback loops. However, DevRev is less appropriate out of the box for teams that sit outside those core functions, as the platform’s terminology and workflows are opinionated toward product, engineering, and support use cases. Without deeper custom object support and greater flexibility in redefining terms and processes, it has been challenging to demonstrate value to those teams and to help them move away from established tools and ways of working.
Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
Allow multiple different entry points and work flows for as many different needs your teams / company have
The onboarding experience could be improved for teams that are not directly implementing DevRev, as they are often introduced to a powerful platform without enough guided context and can feel overwhelmed early on.
Creating and managing objects, dashboards, and other configurations would benefit from more robust desktop-based creation tools, as current workflows can feel constrained or unintuitive at scale. Use industry standard language and report building.
While regressions are rarely critical, the frequency of small UI issues, such as broken date selectors or text visibility problems caused by theming, creates unnecessary friction and frustration for users.
If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.
DevRev provides strong support through a dedicated key account manager and tech team, making the experience seamless. There might be hurdles, but they get resolved with team support. The tool is also very easy to use, with the user able to customize and use various features as needed.
I have no functionality, reliability, or speed concerns with DevRev. In the past, we raised a few latency issues that were fixed within days by the engineering team. The DevRev team were incredibly thankful for these being raised.
I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.
Online Training from Atlassian was really Good to effectively deploy, manage, and utilize Jira Service Management. It really improved the overall Operational Efficiency and productivity of end users in the organization. Training gives the confidence to use Jira Service Management for all of the Product engineering, Application support, and Infrastructure engineering support team members.
Online Training was good and informative for new users adopting Jira Service Management. The Training helped to understand the product features, customization capabilities, and integration options with various tools in an enterprise organization, so the overall productivity and efficiency are improved at Blue Yonder. It also helps to timely address the incident tickets, user stories, and track and close them in a timely manner.
Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.
While Freshdesk and Kapture are great tools, they lack advanced features such as agent assist and AI summarisation. Dedicated support at these companies also becomes an issue, as no dedicated team is allotted due to frequent changes. Also, these tools are not DIY kind and require external help for use and excellence.
DevRev is incredibly flexible - while we started with a support and product move to the tool - Engineering, Finance, People, and our Account Management team quickly followed. The best part about these teams being in DevRev is tying everything back to the customer and being able to build intuitive, flexible workflows for any need.