“New and improved” is one of my favourite slogans. How can something be improved if it is new? Sure, I understand what they mean, but you simply can’t have both. The dashboards in 3.3, however, are both new and improved. Promise.
Dashboards are the widget-based overview pages you can set up for your own homepage and project landing pages in The Bug Genie. They contain various tidbits of information, such as “recent activity”, download links, live statistics and more.
Wanna see how they’re new and improved? Hit the break for more information.
Aaaaaand we’re back. We hope you’ve liked the changes announced for the wiki and issue view already, but today we’re showing off another awesome feature in 3.3 that will likely change your issue tracking workflow for the better: @mention support!
If you’ve used twitter, facebook or any other social application in the past few years, you’ve no doubt seen support for mentioning users by typing an “@”, followed by the username. Read on to see how the @mention support will make interacting with other users in The Bug Genie easier!
Most of you have used the wiki in some form or another. Whether you use it or not, a wiki can be an invaluable tool when it comes to organising project documentation, articles, files and a lot more. Having good wiki tools available is really important, and 3.3 will finally bring the suite of wiki tools up to par with the rest of the system.
So, let’s have a look at how wiki editing is improved in the 3.3 version, compared to 3.2, shall we?
(for an in-depth look at the new syntax and functionality, see the previous article about wiki improvements)
One of our main goals with The Bug Genie is to make your life easier when tracking issues. To achieve this, we’re constantly looking for ways to improve. Closing in on the beta release for 3.3, we’re fine-tuning our final adjustments in the issue view, and wanted to share with you how this has been changed between the current 184.108.40.206 release and the upcoming 3.3 release.
Read on for more details!
Today our brand new websites, thebuggenie.com and thebuggenie.org has finally gone public. This has been one of the main reasons the upcoming 3.3 release has dragged on, since we wanted to have a new and stable environment to support us going forward.
With our new thebuggenie.org website, we can finally put some more effort behind some long outstanding community contributions, such as the excellent translation job done in our translation team, highlight select contributions, and do more with our code repository.
Our brand new thebuggenie.com website fleshes out the functionality found on our old website, but also adds some long-awaited features such as an online, up-to-date, searchable knowledge base, training courses and a new account management panel for all our hosted customers.
It may still take a little while for the DNS pointers to update, but we do hope you like what we’ve done. Either way, please let us know via comments here, or via email: email@example.com
Last week, we released version 3.2.7 (and 220.127.116.11 to hotfix an upgrade and installation issue). This release is a collection of all the development that has happened in the 3.2 version since last release which was almost a year ago.
There’s no need for releases to be this far apart, and we’ll try to not let it happen in the future. In the meantime, in this release you can enjoy:
- Improved speed and stability
- A whole slew of translation improvements
- Support for PHP 5.5
- Support for logging in via Mozilla Persona
- General bugfixes
Until next time!
This blog post will start out with an apology. The Bug Genie version 3.3 has taken considerably longer to finish than I first imagined. Most of you who follow The Bug Genie are familiar with software development. As is often be the case when you are working on a growing project, areas of the code and the application needs to be improved and added to, in order to both maintain scalability, usability and to add and improve features.
The Bug Genie has been at a stage where a lot of the backend code needed to be refactored and to be improved. There are several things and features with The Bug Genie that are really awesome, but there are also quite a few areas where we simply aren’t doing our best. Notifications, authentication, permissions, file uploads, mobile – these are just to mention a few. In the age of html 5, usability first and “competing” software improving at a rapid pace, The Bug Genie needs to both lead and follow. Lead, by showing that open source issue tracking and project management can look – and be – as good as proprietary alternative. Follow, by not lagging behind in features or usability.
Version 3.3 started out as a medium-sized improvement over 3.2, about the same as 3.2 was over 3.1. There was a time during 3.2 development where using 3.1 was becoming a pain. The improvement in features and functionality in 3.2 was just too much to keep using 3.1, once you’d made the switch. This is where 3.3 has been for several months. Version 3.3 – as an improvement over 3.2 – is more than finished, but it’s not there yet. There are still things that needs to be addressed, improved and changed. I’d like to keep improving and fixing, but at some point you gotta say “dude, release it already”.
3.3 just won’t be all it has been promised to be during the last year of development. Too much time has gone since we started, and too many things have happened to keep our initial targets. But it will be a great improvement over 3.2 – so much, in fact, that I can almost guarantee that you will have no reason or desire to switch back.
Now, for the update. During the last couple of months, the search frontend and backend have seen a complete rewrite with focus on finding issues immediately, instead of old-style “searching”. You’ll see what I mean once you get your hands on the beta. Also, mail notifications have been improved, with the introduction of “notifications”, and a much simpler notification setup for email notifications. In addition to that, a great number of improvements are happening in the backend to improve performance and security for all our users and usecases. In addition to this, the default theme has seen several tweaks and changes to improve readability and usability.
I’ve attached a couple of screenshots of how it currently looks. Keep in mind that some of this may still change, but I think it’s starting to look solid. I hope you like what you see – and if you want to help out with development or testing, feel free to check out the master branch on github.com/thebuggenie – pull requests are highly appreciated.
Until next time!