Jira Service Management vs. PDQ Deploy & Inventory

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

PDQ Inventory is great if you have a local network of computers on or off a domain. As long as you have a way to log into them with common credentials. Great for large organizations, particularly ones interconnected with VPNs. PDQ Inventory isn't so great for PCs that aren't connected to the same LAN the server is on. (i.e. non-vpn remote users) They used to have a remote agent you could install, but it was removed after numerous issues.

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

• Push out new software
• Push out Updates to current software
• Push out patches and updates that we don't have other ways to push out
• Keep end-users updated with little involvement

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

• As good as there email support is.. would like a live operator option
• Some updates are hard to understand when 5 versions of the same program exist
• Thats about it, PDQ deploy is the best out there

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

PDQ is very useful and one of the tools that we use a lot.

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

Logical - If I want to do something with the software, it is quite clear on how I need to go about that. There isn't some weird process that is proprietary to just that vendor and is counterintuitive. What I want to see is displayed with just a couple clicks.

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.

The built-in help menus and general ease of use render whatever systems support there might be almost irrelevant. There is stability in the system's simplicity; if you're in the position to use such a product, you're your own best friend. Simple web searches more often than not turn up the solution to any little niggles, such as what silent install switches specific applications require (a remarkably wide choice of options exist). System updates are timely and unobtrusive, installing in no time at all. Maybe I've just been lucky; if so, long may it continue!

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

This software was referred to us by an IT professional. Previously, we were installing the software with the help of remote desktop applications but it was very time consuming; it was wasting the user's time since he could not use his computer. After testing PDQ Deploy, we just never looked back.

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

• Speed of deployment is very positive for new software setup, saving hours of testing and deployment locally
• Made patching for large computer estate very efficient, another positive for staff not having to spend hours of patching individual machines
• Works well for small team of IT's and again makes various repetitive tasks much easier

Incentivized