We performed a comparison between Alemba vFire 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."Incident Management is the most valuable feature of the solution."
"The workflow is very good, as well as customizable."
"When we met with the Alemba vFire from Australia, it was a good discussion and they have a good feature roadmap."
"The solution offers lots of information on the website to assist with technical queries. There are also many community sites to help you troubleshoot any problems."
"Jira lets us customize the workflow to meet our requirements. The email and alert features are also handy."
"The links between the help desk and Jira issues and between Confluence and Jira issues are most valuable. I can write requirements in Confluence and link them to user stories in Jira and test cases. I can see my test coverage and all that kind of stuff. The integration between these three is very useful. It is pretty customizable, and it integrates well. There are a lot of add-ins and a lot of connectors to third-party products. In my last company, we used Test Royal for managing all the tests, and it integrated perfectly with that. For any issue or bug, we could see what tests have been run and the complete history of the tests."
"We have an Agile environment and using Jira makes it easy to adhere to Agile best practices."
"Developing processes is easy and user-friendly."
"We use JIRA Service Management for tracking purposes, planning, and execution."
"Jira gets the basics right in terms of the product backlog and a scrum board teams can use to manage sprint backlogs."
"The most valuable features are the management tools."
"The reporting needs to be improved."
"The product should improve its ability to integrate with third-party tools."
"We had issues with the user interface, the way it was structured wasn't that user-friendly. The chat features could improve. For example, in change management, all the chat discussions can be done via ServiceNow. We are using two separate solutions, such as Teams, to chat, and the Alemba vFire tool to process."
"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."
"I would like to see the user interface changed, it is not very user-friendly, and it transitions workflows."
"The solution needs to be integrated better with Office X5."
"In-built chat is missing in JIRA Service Management."
"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."
"It would be useful to be ale to link tickets across different gantt charts in Jira and Confluence."
"Its UI is a bit overwhelming for new users. That has been the problem with Jira for a long time. If they could put some fields that we could use to simplify the UI, it would be good."
"I feel that Atlassian isn't really interested in fixing everything because if they did, the partners that are developing the fixes and features would not have a place in the market."
Alemba vFire is ranked 27th in IT Service Management (ITSM) with 3 reviews while JIRA Service Management is ranked 2nd in IT Service Management (ITSM) with 73 reviews. Alemba vFire is rated 7.4, while JIRA Service Management is rated 8.2. The top reviewer of Alemba vFire writes "Fulfills all IT management needs, simple setup, but could be more user-friendly". On the other hand, the top reviewer of JIRA Service Management writes "Customizable, stable, and integrates well". Alemba vFire is most compared with ServiceNow, whereas JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, Freshdesk, BMC Helix ITSM and PagerDuty Operations Cloud. See our Alemba vFire 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.