Jira Service Management vs. Odoo

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 is well suited for inventory tracking, shipping and sales work flows. While some customization is needed to make it functional, if done correctly Odoo can serves as a powerful one stop shop for all of a businesses needs. The ease of customization for email templates, both for sales communications and marketing outreach leaves something to be desired. Perhaps our team hasn't explored this fully enough. I have personally found it intimidating in trying to construct a news letter using the email marketing module

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 creation of products is extremely simple, I like that it does not complicate you to put a lot of detail, of course if you want to put more detailed information later it allows you to do it without problems
• The fact that I can manage my inventory of my warehouse is very convenient, I only generate my stock report of the products we have in stock and taking inventory is easier
• The management of opportunities in the CRM is also great, because the guys from the sales department generate their opportunity, place what their client is requiring and we, the logisticians, can automatically generate the quote for what they are requesting, and from there they can only download their quote and send it to their clients.

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

• Customer service is nonexistent. You will need a 3rd party to assist you.
• The system has an open app for integrating with other programs. These are developed by third parties and can be hit or miss in functionality.
• The system offers great flexibility; however, it is too much and requires coding. For example, changing a Sales order PDF requires coding to modify the document.
• Initial implementation is clunky and seems to require a 3rd party just for setup.

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

Once you complete the training with Odoo, you have a great grasp of how the system works, and most every feature is intuitive- There is rarely a task within Odoo that I get frustrated trying to figure out- I can typically look through the system and find what I need to do, and if I ever do need support, the Odoo Support team is excellent

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.

Easy - there is NO SUPPORT (like in ABSOLUTELY NOTHING!!!!!!!). Even for legally mandatory requirements where the system MUST work, they will gladly take a month to get back to you with a NON-answer. We couldn't even get our bank statements correctly into Odoo for 2 months - leading to no reconciliation and the company accounts were a mess (still are!!) as a result - Completely irresponsible. Have not EVEN had an apology from Odoo - they couldn't care less !!

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

We decided to go with Odoo over Netsuite due to a few factors. Price was a big reason why, Netsuite is the most expensive ERP we vetted. I also did not have a great experience with Netsuite at my last job. I was on the roll out team and it did not work as promised for POS, inventory managing or reporting, it crashed constantly in the middle of using it. Just over all very poor. Considering it is owned by Oracle and the most expensive, you would think it would be able to function on some sort of base level. That company ended up terminating their contract with Netsuite early and going with a different company.

We don't have crashing or error issues. I can complete receives, cycle counts etc and all of my information saves. Visually, Odoo is more satisfying also.

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

• In older versions, it was super expensive to make it even work. You had to hire third-party developers all the time.
• Newest versions have better built in functionality.
• Cost is pretty high. Odoo plus developers to support it could bankrupt a small business.

Incentivized