Slack is a group messaging or team collaboration app that aims to simplify communication for businesses. Features include open discussions, private groups, and direct messaging, as well as deep contextual search and message archiving, and file sharing. Slack integrates with a number of other tools, such as MailChimp, Dropbox, and Google Drive. Slack was acquired by Salesforce in December 2020.
The product is free to use, and also has paid plans with more features and greater controls.
The…
$0
per month per user
Pricing
Bugzilla
Slack
Editions & Modules
No answers on this topic
Free
$0
Pro
$7.25*
per month per user
Business+
$12.50*
per month per user
Enterprise
Contact Sales
Offerings
Pricing Offerings
Bugzilla
Slack
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
*Per active user, per month, when paying once a year.
Pro is $8.75 USD per active user when paying month to month. Business+ is $15.00 USD per active user when paying month to month.
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but …
Buzilla is easy to use and provides basic functionality to use as a bug tracking tool. If big size attachments are allowed it would have been great. Also with Bugzilla home->Test management area is improved by allowing multiple sections it would be awesome!
I would definitely recommend Slack to everyone who needs a messaging platform for work. The thing that I most appreciate on Slack is the possibility of talking to my coworkers without using my personal number or personal apps. This way, I can separate what is work and what is not. Slack even has the option to mute notifications after work hours. I'm able to keep track of every project and discuss them in an easy and fast way. Another great thing is that you can keep and check the history of channels and groups, this way the discussions are never lost when someone joins the project in the middle of it or someone leaves, the history is always there. The only thing that bothers me in the platform is the system of threads, where you can easily lose the messages cause they look kind of hidden. If you have multiple subjects with someone and the person only responds in threads, it's very common to lose their messages.
Open source! No license fee involved, no limit to the number of licenses.
Easy to install and maintain. Installation is very easy and hardly needs any maintenance efforts, except when migrating from one version to other. Each project can have its own group of users.
Includes all the core features/fields that are needed to log a software bug/issue.
Multiple attachments are possible, supports various formats.
Good for reporting. Filtering mechanism lets you query bugs by various parameters.
Cloud Based. I'd like to see bugzilla be cloud based. The company I currently work with made a final decision to change db's for this specific reason. Due to the frequency of travel in this company, they need access to bugzilla from differing national / international locations.
Larger File Attachments. I believe the limit of a bugzilla content upload is 4 megabytes. For many of our video'd issues, this file size is simply impractical without the additional effort exertion on video compressor applications.
While threads exist to keep conversations organized, managing and finding threads within channels can be cumbersome. Enhancements in thread management and search capabilities could be beneficial.
Slack has a limit on the size of files that can be directly uploaded. Increasing this limit or providing smoother integration with external file-sharing services could be beneficial.
Managing guest access can be cumbersome, and simplifying the process for inviting and controlling guest users would be beneficial.
Slack primarily operates within individual workspaces, making it challenging to collaborate across different workspaces. Enhancing features for inter-workspace communication could improve collaboration for organizations with multiple Slack instances.
For future projects I will look at something that is hosted in the cloud that I don't have to manage. I would also like something that has a more modern feel to allow my customers to use it as well as my employees.
As useful as Slack has become within our company, I feel fairly confident we will continue to use Slack as a communication tool. They continue to improve their software and add value to its use within our office. Customer service delivers, which is an absolute must. Looking forward to how they improve.
This is a pretty straightforward system. You put in the bug details, a ticket is created, the team is notified. The user interface reflects this very simple and straightforward flow. It's certainly much easier than trying to track bugs with using Excel and email.
As long as you use the basic chat features and nothing more, it really is super easy to understand and use. Once you want to take advantage of some of the more advanced features and capabilities, that's when things get complicated. Anyone who has use SMS or a chat program before will be able to figure out the basics though, so rolling this out should be relatively straightforward and not required exhaustive training. Teaching chat etiquette is something else though.
Since it is open source, it doesn't have customer service. However, the amount of information on forums is vast. If you can wade through it, you'll get what you need
I've never had to contact support for Slack which is a great testament to its ease and use. Adding people outside of the organization takes a little getting used to, but ultimately allows for greater collaboration between FTE and contractors. There is no clear alternative to this software, so it's the best we can do for now.
Implementation was pretty simple. Particularly because the product cannot be customized so there is not much to do apart from getting it up and running.
It always helps if you communicate to everyone in the organization how important it is to drop whatever other chat tools they are using and jump quickly to Slack. They will all fall in love with it.
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but because the organization was looking for cost savings, we ended up going with Bugzilla and it's FOSS model so as to avoid ongoing costs.
Microsoft Teams got very confusing for me with all of the tabs and different things to learn how to use it. I felt that Slack has a much cleaner look and makes it easy for anyone to learn how to use. I also like how it integrates seamlessly into our Google/mac workspace!
It has made the SDLC process more efficient. Bugs were logged and tracked in emails or in Excel sheets leading to slow communication and at time version issues with multiple files. Being an online tool, Bugzilla solved those issues, improved communication, instant status updates and improved efficiency.
We have used Bugzilla with a lot of federal goverment agencies (DHS, CMS, SAMHSA, CDC, HHS etc). Project Directors adn Principle Investigators were at times given access to Bugzilla which provided a snapshot of open vs closed issues.
Some groups would resist using Bugzilla with the email reminders being the main reason. Turning off or reminding them of features where we can 'control' email notification helped a lot.
