Jira Service Management vs. Ziflow

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

We work with a lot of cross functional teams, so it is nice to have them review things on their own and provide feedback all in the one place for our team to review. It helps cut back on meetings and emails full of feedback that gets lost. This is especially helpful when we are working on our catalogs. We do reviews on Ziflow all the way from rough layouts to proofreading.

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

• Simple and user friendly interface with little if no learning curve.
• Accurate and specific change requests are especially enhanced when using the markup tools.
• Nice to be able to assign who the decision maker is and also be able to change project participants easily, like when someone goes on holiday or sick leave.
• SOCD (sent, opened, comment, decision) progress indicators provide an awesome 'at a glance' view of project participants activity.
• Email notifications and integration with ASANA is brilliant.

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

• Comments with instances that span multiple pages force you to zoom out, which can be rough on multi-page proofs. We end up making a comment on each instance for ease of review.
• Maybe it is in there, but I would love to be able to upload a new version and review/make comments before any of the other reviewers can see it—to double-check for errors. Maybe there is a verification stage first before releasing it to the other reviewers.

Incentivized

Ziflow is easy to use, efficient and now is also part of our daily lives. Hence, the teams are already adapted to the tool and willing to work with it. The features are according to all what was expected and we had a great experience until the moment with the tool

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

The tool is easy to use for digital oriented people. For the ones not used to this kind of environment, it could look a bit complicated at the beginning, but following the instructions and tutorials and performing it once makes you get a grip of it in just one use.

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 ZIflow support team has always been very responsive to my questions, issues and other problems. The good thing is I have never had to use their support team all that much because Ziflow has been for the most part trouble free. If it had been error prone, we would have dropped it long ago.

Incentivized

They were friendly and took the time to go through everything, especially relating to how we would use the system.

Incentivized

It was seemless! Things got instantly better when we started using Ziflow!

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

I found Ziflow to be much better than PageProof in several ways. The tools available for making comments and edits are more intuitive and there is a greater variety of tools and the version control features worked much better as well. Also their customer service was far better when it was necessary to interact with the company

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

• Improved efficiency and time saved in making proofs and adding people to proofs with staging and template features.
• Robust proofreading features for reviewers like comparing previous versions.
• In my experience, customer service is quick to help with issues or outages (which aren't often).

Incentivized