Atlassian Jira is a project management tool, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
$81.85
per month 10 users
Jira Service Management
Score 8.2 out of 10
N/A
Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
We selected Jira Service Desk because we were already Jira users, and the price point was easy to absorb. Our experience as Jira administrators made it easy to customize Jira Service Desk to our needs.
Compared to other products I have used, like, Fresh Desk Service or Manage Engine it has more features included per user and technician (others may require a license for each type). Portal setup can be integrated to the Confluence Portal for easy access to Jira for service …
Jira Service Desk has similar or equivalent features to heavyweight competitors as HP Service Manager, for a better price. The highlight of Jira Service Desk, in my opinion, is that you can customize a series of visual boards that are tremendously useful for an agile and …
There are other systems that perform well, but we always came back to JIRA. One of the reasons is that it has companion systems like Confluence that can integrate and be used with it. Another reason is JIRA can be molded to be many things, not just project management. For us, …
ServiceNow has many of the same features of JIRA. Teams within the organization use both ServiceNow and JIRA, but we primarily use JIRA. We chose JIRA because it seemed easier to set up the linking of related tasks and projects together, but other teams have said the same thing …
JIRA stacks up very well in particular with Microsoft Team Foundation Server which I used extensively for 7 years. The transition I had to do to JIRA was seamless and they both compliment each other well.
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 …
When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into …
Sure there are other great service management products in the market. Since we use JIRA and Confluence heavily, Service Desk fits perfectly in the suite. As a brief example, after the customer creates a case, we can create an associated issue at JIRA for development team, after …
I think JIRA is best suited for IT tickets and service requests. Comparison is hard, but I use JIRA on a daily basis and I cannot think of a better alternative for the task we are using it for.
We used a MS product called SCSM which was very old and hard to use. The UI was rough and we had to find a lot of workarounds to make it work like we wanted it to. Service Desk was the main product we looked at since we already had JIRA and Confluence.
I think JSD is better than all of the similar ones I have used because it allows for greater customization. It is also really geared to submitting bugs and enhancements, where the other products are more about the software development workflow and project management.
It's out of the box the best option I could imagine and by-far better than any custom-made tools I've otherwise seen. Also thru its modular setup, it can be extended and upgraded as you go so the system adapts to your changing business requirements. Only downside is - without Co…
At the time we chose JIRA Service Desk, we had been using GitHub to track project issues and features. We were looking for something that would add more project planning features and allow us to put more project information together in one place. JIRA succeeded somewhat in …
When we completed our merger with another company, they were already using Jira so it made sense for us to use a common solution. Their experience and investment with the package was a major factor in choosing it over our current tools and those we were researching for future …
We evaluated Remedy's ServiceNow as well as a few homegrown solutions (in SharePoint and in JIRA Software), and found that Service Desk's integration into the rest of the Atlassian suite of products was the best selling point. We already were licensing a number of Atlassian …
I've tried many other systems and used them extensively in the past including GLPI with integrated software and computer inventory systems. Used OTRS for customer related ticketing (in comparison to using Service Desk for internal ticketing) and found the system not geared …
We tried to make Clarizen a ticketing system and it just wasn't built to handle all of the different scenarios we required. Hesk is very limited and an OK ticketing system for internal use with simple tickets, but does not offer the same level of customization as JIRA service …
Jira facilitates software development, bug tracking, and sprints. It's ideal for structured workflows, issue management, and customer communication. However, more straightforward tools might be more efficient for highly creative, unstructured tasks or tiny, agile teams with quick visual overviews. Jira's complexity can be overkill for basic task lists.
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
Integration of tools like Bitbucket, Github, etc., has made it easier to track the code changes, pull requests, and branches linked to the respective ticket.
The detailed tracking system in JIRA has helped the teams prioritize and understand the project tasks and issues.
JIRA's project tracking board helps you keep track of the project, its flow, and expectations in a structured format.
Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
Request forms are very basic and there is no native dynamic field ability available.
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
The interface is simple and easy to use if you have some experience with it. Configuration is also logical most of the time. However, less experienced users tend to find themselves lost in some tasks - usually complex project configuration- but sometimes simple things, such as seeing why a user can't move issues in a workflow. Jira configuration requires a good amount of experience - and even experienced users often resort to documentation. It's a tool that's easy to use if you know what you're doing and where to find the proper documentation, but novice users tend to find it challenging.
Jira Service Management tool will serve it's purpose to do what it is meant to be. It has it's own limitataions on few features, however it's the industry standard ticketing tool. All covers all the processes that required to resolve the issues. It has various use cases in incident management, Request management etc.
Did not face any issues and whenever they plan maintanance they update all of us very well in advance also so in that view we are good with the product stability.
Performance is really good though it holds lot of data it loads quickly especially search operation also get the results very quickly as needed hence its good
I have not had a chance to contact JIRA's customer support. It does offer extensive documentation, although it often feels too technical for me. There is also a JIRA training app that lets you take little lessons and quizzes on different areas (e.g., JIRA basics, agile). I did find it a helpful way to teach myself.
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.
Had received training from our own internal user so it was good and also very easy to understand topics and many tasks in the UI are self explanatory and we can do by our own
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
monday.com cannot be integrated with CI/CD tools, whereas Atlassian Jira integrates with CI/CD tools seamlessly. Atlassian Jira has strong Agile and Scrum support. Coming to monday.com, it has basic agile functionality. But Atlassian Jira has a complex UI, and monday.com has an intuitive, drag-and-drop interface. Overall, Atlassian Jira provides features like Agile project management, DevOps integration, and customizable workflows.
When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.
Atlassian Jira's robust workflow automation has boosted team efficiency, shortening delivery cycles and driving a positive ROI through improved project management.
Its advanced reporting and integration capabilities have enabled data-driven decisions, aligning operations with key business objectives.
However, the steep learning curve can delay adoption, potentially hindering short-term ROI.