We performed a comparison between 4me and JIRA Service Management based on real PeerSpot user reviews.
Find out in this report how the two IT Service Management (ITSM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I like their request management as well as their project management."
"The multi-tenancy architecture, both in terms of functionality and reporting, is the best feature. It is a really well-thought, designed, and developed part of this product."
"It offers a comprehensive set of features without requiring additional payments for each feature."
"The solution is highly stable."
"JIRA helps integrate Kanban Board features and for this reason what it does it does well."
"Service Management is great if you're an Atlassian shop already using JIRA for the development team and you want another tool for help desk ticketing. When it's all under the same umbrella, I can easily take a ticket from the help desk and move it to the development team. You can't beat that integration between two products."
"The SLA, speed, the comments from agents' side, and the dashboard for agents are the most valuable features."
"I find the Kanban chart where we put each story in to be the most valuable feature. We use the Kanban chart to revise the project every morning in our five-minute meeting."
"The initial setup is straightforward."
"Reporting and easy export to Excel spreadsheets."
"It has improved our work in a number of ways. First, it has made everything much faster. Before Jira Service Management, it could take weeks to resolve a ticket."
"We get software developed faster."
"One area where I believe there's room for improvement in the 4me system is the absence of an asset discovery tool."
"We're still biased towards our previous, more mature product. 4me still needs to reach that level of maturity."
"We would like to be able to customize and brand the solution, or at least the majority of its features and dashboards, particularly those that will be used by a large number of people."
"Asset Discovery is a feature that should be added."
"I'd like to update the dashboard so that more features are available."
"Integration possibilities with other products that are not Atlassian would be helpful. Support should also provide separate installation guides for each product even though they are easy to install."
"The product could improve its asset management."
"Integration could be improved."
"From the customer side, it's not friendly used compared to other competitors, like ServiceNow or BMC. It's also not fully ITSM management if you compare it with ServiceNow or BMC. They have a full model of ITSM. In BMC they have TrueSight, they have Discovery, which helps IT to discover IT equipment with a serial number, with the specs, capacity of the server."
"The performance in cloud service management could be improved."
"The way it handles subtasks can be improved. We would really like the ability to have different types of subtasks. If we have a user story for a feature, we would like to have a subtask for documentation, a subtask for requirements, a subtask for development, and a subtask for testing. Right now, we just make four subtasks, but there is no way to specify their type, so we have to add a custom field to specify what type of work is this. It just means you've got to look at more data. For logging time or time tracking, we would like to have something using which we can define the work type we're doing. We would like to log whether we're working on a bug, a new development, scope change, or rework. We've got a user story for which we do the dev, and then we have to do more dev. It is the same story, but some of it could have been a scope change, and some of it could be a rework because we either screwed up the first time or missed something obvious. Currently, we have to have a custom field and track that separately. It would be nice to have some kind of work type for logging time."
"If I need a new feature, JIRA requires me to pay for all users when only specific people use that add-on. I should not have to pay for everyone, so this is an area for improvement."
4me is ranked 19th in IT Service Management (ITSM) with 4 reviews while JIRA Service Management is ranked 2nd in IT Service Management (ITSM) with 73 reviews. 4me is rated 8.0, while JIRA Service Management is rated 8.2. The top reviewer of 4me writes "Impressive scalability and reliability for seamless service management". On the other hand, the top reviewer of JIRA Service Management writes "Customizable, stable, and integrates well". 4me is most compared with ServiceNow, ManageEngine ServiceDesk Plus and Zendesk, whereas JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, BMC Helix ITSM, Freshdesk and PagerDuty Operations Cloud. See our 4me vs. JIRA Service Management report.
See our list of best IT Service Management (ITSM) vendors.
We monitor all IT Service Management (ITSM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.