Jira Service Management vs. TeamDynamix IT Service Management (ITSM)

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

TeamDynamix is great for any organization that has established any kind of support group, whether it's in IT, project management, facilities, etc. This tool can also aid in tracking decision making with its change management abilities. The added knowledge base system is also a huge improvement to any company, as there is now a searchable database of information that use to only live in other people's minds. If you are willing to put the effort and work into the system, it can prove to be a very valuable addition to your toolbelt.

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

• Integrates with external systems
• Allows for customized reports
• Provides tools to customize the product to meet your needs

• 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

• Needs the ability to show ticket submitters who owns the ticket
• Needs dark mode
• Clicking on a ticket to manage opens a new window; can get lost with hundreds of open windows without knowing

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

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.

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

Because it gives the total time and fetched taking after for laborers to
give the advantageous payrolls and alter the charge sheets with correct
information and friendly tool.

• 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

• We have already been able to have insight into how many tickets for service requests we do in any particular time frame. We were surprised to find that we had as many as 300 tickets on our small support team in just a month's time.
• We can centrally locate all of our how-to documents and other information that usually lives just in the memories of our employees. We have hundreds of documents that will now not be spread over Teams, workstations, and document folders but will be centrally located and searchable for years to come.

Incentivized