Issuetrak vs. Jira Service Management

If someone is looking for a ticket management system or something to keep track of records in a cloud environment, IssueTrak is well suited to handle this need. It's a very simple and basic approach and after using it for 10 years, it is still just as easy to find what I'm looking for on previous tickets from years ago. The setup can get a little bit of a challenge and if you have a need to segregate users/employees into their own areas for workflow, it can be a little daunting trying to get it just right. Where I feel that IssueTrak falls short is if you need to keep track of CUSTOM FIELDS (fields that you input as searchable and trackable information) in the Dashboard area, where you spend most of your time looking to see what your workload and flow are like, is very limited, requiring you to dig a little further for what you want to see. Also, no ability to input physical addresses / GPS coordinates to be displayed on some sort of real-time map is also missing and could really boost what IssueTrak has to offer.

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

• Keeps expansive records over a large period of time.
• Provides a simple way to look at your workload with dashboards.
• Can be used on a company level with employees, but also can be set up to have customer interaction.
• Additional modules are handy as well (Inventory tracking, Surveys, etc.)

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

• No place to physically MAP out your tickets (IE: Google Maps / Address Fields / GPS coordinates).
• Dashboards and ticket items do not update in real-time, making users need to REFRESH to for the latest updates/dashboards.
• Mobile app not as good as the desktop experience, especially for Dashboard views.
• Can be a bit complicated to setup and get going. Segregation of departments / users can also be a little on the complex side.
• Dashboards could GREATLY use the ability to display and track CUSTOM fields for quicker access to the information you want the most.

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

IssueTrak is good at what it does, but we really needed some expanded functionality out of it that just hasn't organically happened. Having a 'real-time' update of Dashboards and tickets is a piece that is lacking, especially as our organization continues to grow. A lot of times you go to update a ticket and find out it has been altered/closed before you even hit the submit button. Being able to make charts/graphs of custom fields for Dashboard is a feature (that I feel) is long overdue. Also, the ability to capture address information / GPS coordinates to be displayed on a live map is also a feature we really wanted to see.

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

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

They were always very good at getting a timely answer to any questions I had and in cases where I actually needed support to step in and help, they always delivered. I was very happy with the support I received from them.

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.

IssueTrak shines for basic ticket management and the format in which they display all the information is very well done. I'd highly recommend it to someone that is looking at trying to track information at a ground level (just starting out). While other solutions are not perfect by any means, we just find that it is lacking some key features that we had hoped would have been implemented over the years (IE: More flexibility with Dashboard reporting and custom fields, a way visually look at addresses and GPS coordinates on a display map, more of a real-time approach with data and completion, etc.) This need caused us to look at some other solutions that may fit the bill a little better in the future.

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

• Made tracking individual service changes, adds, deletions, and trouble-ticket very easy to manage.
• We migrated from a paper-based work order system to completely digital and online, thus cutting down on a lot of unneeded printouts.
• Was able to actually validate and see the performance of users and what they were contributing to the department on a daily, weekly, and monthly basis in terms of work performance.

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