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
Khoros Communities
Score 7.6 out of 10
Enterprise companies (1,001+ employees)
Lithium Community is a fully-featured community platform and is focused on the needs of marketers. Lithium most often competes with Jive Team Collaboration and Get Satisfaction.
N/A
Pricing
Jira Software
Khoros Communities
Editions & Modules
Standard
$7
Per User Per Month
Premium
$14
Per User Per Month
Free
Free
Enterprise
Contact Sales
No answers on this topic
Offerings
Pricing Offerings
Jira Software
Khoros Communities
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Pricing is variable based on the needs of the customer.
Khoros was the best use for our needs and other solutions were always missing at least one or more features that were crucial for our use case and the workaround proposed by other platforms weren't simply enough. Most of them have their strong side and it is hard to say, which …
I evaluated several different community platforms when Jive-x was being discontinued and ultimately chose Khoros as it had much more customization options compared to the other platforms out there. It also seemed to be the most robust and powerful, had the most features, and …
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 describe Khoros as the salesforce of community software in that it's customizable and enterprise, however it can be a beast to use. There isn't any standout in the community field (in my opinion) so if you're looking for an enterprise community software, it'll serve you well. I do think it's important to realize you can't manage this without the proper buy in from your company when it comes to development of the site. You shouldn't be using Khoros if you only have a front end community manager. If you're going all in on community and need a solution that will scale as you grow, consider Khoros amongst your vendors and see how you like it. It's worth checking out.
I feel that the professional services engagements need to be better. There is a lot of miscommunication, and a lack of clear outcomes, goals, and timelines. It can take weeks to get meetings on the books and a team assembled to start getting work done.
Documentation on their website, at times, is outdated or incorrect. Sometimes the product doesn't even work as described in some of their documentation
The admin console could use a nice fresh UI overhaul. While it's functional, it would be nice to see a more modern UI for the area where most community managers are spending a decent amount of time
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.
Community has worked well for over the year. However, there have been a lot more technical and feature issues we have been seeing in last year or so. Also customer support has not been very quick to address issues. SO there are things that can definitely be improved on Khoros end
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.
Like every backend, it can always be improved upon. The excellent thing is that Khoros have a hugely active customer support community as well as a fantastic case management system to triage support issues and requests. So regardless of your level of knowledge or familiarity, you're well supported out of the box.
I've hardly ever seen downtime in any of their production communities. There's the occasional reboot needed for config reasons or if patches are applied, but these take place after customer approval and typically last only a few minutes.
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.
They are responsive and proactive. They are really on top of things. They send personal emails to check in on you. It feels like they really know you. You only get emails from 3-4 people at Khoros – they must be customer assigned.
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.
It was out of the box training - pre-recorded/ not live. There was nothing for more advanced topics like APIs. They do have a good knowledge base and community that you can access and folks in there are responsive. I would however like more advanced training options.
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.
We were up against a hard stop with Jive’s contract ending and Khoros connected us with a deployment partner to do accelerated deployment using a template approach. It could have happened in 2 weeks. We did not end up going that way since we wanted more customization. Lithium handled technical stuff like migration, but a lot of the process is self-deployment. It’s one of the ways they teach use of the system is having the user self-implement.
Overall, the implementation was super easy to do. Doing single sign-on (SSO) was the only hard part. The implementation ended up taking nine weeks total, but in hindsight, we could have done in it six. Most of the implementation time was spent in course work, which consisted of on-demand training - approximately 7-8 hours that you are required for you to do, before they turn on the system. During this nine week period, about 50% of my time was spent on implementation.
We had a deployment manager who we were able to email 1-1. I leaned on him heavily. He was great at all hours, for example, they would call back at 7pm PST. They were very responsive.
Content migration strategy is important to consider. Moving from an existing community you need to strategically choose how your layout will be. Two different systems will have two different ways to format communities. For example, Jive has communities with sub-communities, whereas Khoros has community, category, and boards.
Contact migration is also an important consideration. You need to think through how you are going to move contacts from your old community to a new one. For example, are you going to create new logins and passwords? We were hoping to use the integration with Salesforce.com to be a portal, but ended up using an in-house solution that works well to maintain same the same logins. The next related question is are you going to be able to keep them connected to all the posts in your old community? We migrated old posts. If you have a tech-savvy team, you can do a self-migration. Khoros has a migration services team that we utilized. It cost us $10k to move content and posts were kept tied to the user.
The next consideration is your launch/promotion plan. Khoros helped us out and gave us a lot of examples. They shared pre-launch email dates, follow-up emails, FAQ pages (e.g. to explain why switching, why better).
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.
WordPress, Guild, tribe - all have pros and cons vs Khoros. The primary concern of Khoros vs other platforms is cost. For the price difference, Khoros *should* be a no-brainer choice. No one should ever consider using any platform other than Khoros... so why do people consider other platforms?
The platform is incredibly scalable and provides the flexibility to use it out-of-the-box or customize it to whatever extent is needed. It has very powerful APIs and is built in modular way that allows pages, components and other elements to be constructed easily.
