View the official page for the latest updates.
Over the past few weeks, I’ve been working on a little side project in my spare time. It’s a WordPress theme (go figure), but with a twist. It uses WordPress in a completely different way.
While developing WPBundle, I needed a way to keep track of tickets/bugs I found or created while developing. For a while, I was using Lighthouse which worked great. However, I have a thing about owning my content, so I set off to create my own solution. Initially I was going to create a custom PHP solution, but as I was creating it, I realized that WordPress provided me with everything I needed to make it work.
From the site:
This WordPress theme was designed to allow the creation, and tracking, of tickets. It was kept simple, and packaged lightly, allowing the user to use it however he/she wants. Just the essentials have been added, and the rest is up to you.
The idea is to provide a base “framework” of sorts, that creates the core functionality needed for ticket tracking, but leaves room for the user to take it in any direction they want.
I’m sure there are many bugs, but that’s why I’m doing a soft release here first. I’ll update any bugs that are reported (email me at [spencerfinnell (at) gmail (dot) com]) then upload it to the WordPress.org Theme Directory.
Download: Quality Control 0.1
62kb — Last Update: August 25, 2010
Demo: Launch Demo
Send me a note on Twitter if you find a bug, or like the theme.
Remember, there is no sort of protection or anything with this. It just uses the built in permissions WordPress provides. So I’d suggest setting it up in a private/protected directory (unless you want people to see your tickets).
Awesome job Spencer!!
Why are we emailing bugs? There’s an awesome new theme that tracks bugs…
Touche. I was just a little worried of opening it up to the public, as who knows what kind of spam I’d be subjecting myself to. I’ll open it up in a few minutes.
Alright, let’s see how this goes. Post any bugs you find on the demo.
I definitely have to agree with you on wanting to own your own content. That being said: This is awesome! The bug tracking theme looks awesome thus far–can’t wait to use it :).
Thanks for sharing this!
Thanks, this is very good and usable theme.
I’ve just found a bug, when clicking on author’s name on the ticket page, you get this error (but within browser’s URL box):
I would also like to know, how to format the code and set up code syntax highlighting as it is previewed on images above? It isn’t mentioned anywhere.
Thanks once again for so usefull theme!
Download the latest version from http://getqualitycontrol.com
Thanks, that did it (for the author link part).
However, I’ve encoutered a few strange things.
I used 0.1.4 and found out these discrepancies:
1. Pulldown menu is populating also deleted (trashed) tickets, so if you delete some ticket and it appears in the trash, it is still counted within “Status” pulldown as existing ticket, however it doesn’t display those in the ticket listings (confusing)
2. In this tweet http://twitter.com/spencerfinnell/status/24053499560 you released a child theme’s functions.php code to add “projects” to quality control. I’ve used the code an everything seems to be OK, new pulldown nicely appears when posting new ticket, however, whatever you select, it doesn’t work.
If you select some (already created and existing) taxonomy from the new “Project” pulldown at the “Create a new ticket” page and publish the ticket, in ticket listings and on ticket page, there is no “Project” taxonomy selected (so it displays as: Project — ). However, if you edit this using WordPress’ admin background by editing the ticket, the “Project” taxonomy appears within ticket listings and also on ticket pages. Could you please check this out? For me, it would be very helpful to have this option (as I would like to maintain several projects using Quality Control).
3. Still no update on syntax highlighting? Sorry, but provided screenshots (here and also @ getqualitycontrol.com) confused me a bit. If there is no support for highlighting, I will use SyntaxHighlighter Evolved.
Sorry for using this blogpost as a way to contact you, however I haven’t found another way to contact you.
@Mijk: you can set a default project by changing this line in function quality_advanced_form_list_taxonomy() in the child theme’s functions.php:
‘selected’ => quality_ticket_status( …
to
‘selected’ => 123 /* quality_ticket_status( … */
Where 123 is the project id
@Spencer: thanks for the theme. Excellet timing!
I’m having the same issue as @Mijk regarding the project pulldown menu that’s not working. Any ideas on why this is happening would be really appreciated!
I’m not sure why you don’t use the theme for bug tracking, but it’s something you should think about really!
I’ve tried setting it up multiple times, but it just turns into a SPAM fest. Maybe I’ll setup one that requires registration for all users.
As for the projects Child theme bug, I’ve updated it since then, and will post the code on the blog later tonight. Email me (use the contact form) to remind me though!
很好，很强大。
Congratulations Spencer you did a great job. more power