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
Microsoft System Center Service Manager
Score 7.8 out of 10
N/A
Microsoft System Center Service Manager is an integrated
platform that is designed for automating and adapting IT Service Management
best practices to an organization’s requirements. The platform includes built-in
processes for incident and problem resolution, change control and asset
lifecycle management.
Not easy to customize, like ServiceNow, but default configuration works much more stably than SNow implementations I saw. Cannot be implemented as a service and requires underlying infrastructure. JIRA is much more lightweight, but very limited in functionality. At the same …
It has its similarities between the two from a ticketing standpoint but as a primarily Microsoft shop it is nice to have a product that was created to play along with other tools that we are using such as SCCM. We like Jira for the project management tools and Cherwell for …
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.
I think any organization that runs windows on their computers that is size over 50 workstations and looking for a complete package to manage their windows machines must have Microsoft System Center Service Manager, especially if they have Windows servers and VMs. The capability of managing multiple devices at ones can save a lot of time for the IT jobs.
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.
The customer support service is excellent. They help from start/deployment through to any time later on. They responded quickly and resolved our issues professionally and in no time.
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.
We selected MCSM because it is a solid product that we could use very quickly, compared to other tools there is a lot more effort for integration into the infrastructure, costing time and money. We implemented the tool very quickly and since it integrates with other Microsoft products, it was very easy to get up and running.