JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.
$10
per month
ServiceNow IT Operations Management
Score 8.5 out of 10
N/A
Built on the Now Platform, the ServiceNow IT Operations Management bundle is designed to help users gain visibility across infrastructure and apps, maintain service health, and optimize cloud delivery and spend.
ServiceNow has ease of usabilty and configureability. It is smooth and has easy integration with legacy systems. Also, it allows the users to configure and build their own applications.
The Jira software works well for managing scrum boards and allocating resources to a task. When your Epics and Issues are set up properly, it can give you a good idea of where your team stands and the trajectory of your project. It is not the ideal solution if you need to provide documentation and support to people outside of your product teams or organization. It would benefit from having a public documentation or repository feature.
We have taken advantage of the single platform for different IT disciplines over the past few years and now we are doing more and more with the integrations. Our teams are looking at the same information which stops the blame game a lot. Their newest AIOps has been a very nice surprise as we've tried another tool for about 2 years and it required us to hire outside consultants to try and build what we needed. So far, ServiceNow found a lot of things we didn't know to look for. It's not perfect in fixing everything, but really has provided a lot of visibility and troubleshooting.
While there are no fundamental problems with JIRA, I'm unsure that I will be working myself very closely with users of Atlassian Confluence. The client base I am concerned with tend to be more integrated with Amazon, IBM BlueMix / Watson, open source LAMP/PHP (WordPress, MediaWiki) & those that rely on more proprietary CMS would tend to use Sharepoint not Confluence. JIRA seems to me to stand or fall with the rest of the Atlassian silo or suite, as it is not closely integrated with Sharepoint or mediawiki based reporting or knowledge management. Data interchange standards in this area are weak so Microsoft, open source LAMP projects using Phabricator, and Atlassian JIRA seem to be three distinct silos, with Amazon, Google & IBM offering their own tools for similar needs.
JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.
Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.
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.
Jira Software has more integrations and has more features than many of its competitors. While some of its competitors do have better UI/UX than Jira Software, they have improved this greatly over time. Atlassian also acquired Trello years ago, so that adds better user interfaces to the system. They do also offer a pretty in-depth library of how to customize the platform that others don't.
BMC was our legacy system before deploying ServiceNow. It's time had passed for us as it couldn't really keep up with our move to cloud and the number of services we were using. The cost kept getting higher, especially with all of the customization we had to do. Over the years, just got unwieldy. We still use Splunk for raw data and log analysis, but we upgraded to ServiceNow event management and the Loom system log analytics. We had Loom before ServiceNow bought them, but it's nice it's all on one platform for us. Splunk at times had so much info, we didn't know where to start, but ServiceNow gives us a great starting point.
