DevRev vs. Jira Service Management

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.

Incentivized

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.

Incentivized

• It provide AI assistance to our agents i.e. features like summarization of chat.
• It provides advanced workload management using ticket routing features.
• It helps in adding dispositions and is very DIY kind of software.
• It helps in providing advanced Analytics of tickets and dashboards.

Incentivized

• 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.

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

In the current contect the requirments is around having a tool that is focused and can handle large ticket volumes and tracking incident, problem and user requests concerning end users. Jira has built in functionality to address the above practice needs faily easily and has a substantial amount of customizable reports for generating the relevant intelligence.

Incentivized

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.

Incentivized

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.

Incentivized

I'm not aware of DevRev not being available in our two years using the product. The software and support team is available around the clock.

Incentivized

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.

Incentivized

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.

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.

Incentivized

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.

Incentivized

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.

Incentivized

• It helped in reduction of agent count by 5 resulting in 20% cost savings.
• It reduced our average customer ticket resolution time by 50%.
• It helped improved our net promoter score by 5 bps.

Incentivized

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized