Description of the Hack:
This is a basic vBulletin-powered Bug-Tracker
It is based on vB-Todolist originalli created by RekiM who kindly gave me permission to make this "port".
Features
User-definable Types, Severities and States
Front-End fully phrased
XHTML-Compliant
Various possibilities to Filter/Search
Requirements
vBulletin 3 RC2
mySQL > 4.0.2
Please note that this is an alpha release only and I can't and
won't take any responsibilities. Use it as-is at you own risk.
HACK INSTALLATION DETAILS: New files for this Hack:
bugs.php
admincp/bugsadmin.php
Files modified for this Hack:
admincp/index.php
New templates for this Hack:
bugs_addbug
bugs_addbugnote
bugs_listbit
bugs_bugnote
bugs_details
bugs_list
BUGS
New DB tables for this Hack:
bugs
bugnotes
bugtypes
bugseverities
bugstates
> not assign it to anyone or assign the state.
Only members of the bug administrator group can change assignments, stetes, etc.
I don't think i'm gonna make different severities for each bug type. I want to keep this simple.
If you want a fulll-featured bug-tracker better go for BugZilla, Mantis or smth. like this.
Actually, I DON'T want something like Bugzilla, etc. I like this, integrated with vb.
You mind if I take a crack at an addon for creating different severities, etc? I think that's the only thing keeping this from being a truly kick butt mod
I stand by Kirby and agree we should keep it simple. People need something that is EASY to understand or else a feature such as this will not be accepted by the community.
One small request: Is it possible to have a rudimentary "upload' function so people can attach simple jpg or txt files? Sometimes people have screenshots or long error sequences that are necessary to describe the bug. Any attachment is fine but a thumbnail style preview would be a "nice to have" bonus.
Here's a question for anyone who can help. I've implimented this onto a test forum on my laptop and it works fantastic, 110%. I've been asked by my boss to impliment it onto our company website, but it uses vb3 with php3 extensions. Would this still work if i changed the extension, or is it likly to fubar?
@SB2002
The filename is hardcoded into the php-file and templates. So if you change that you will have to change the php and templates also.
@Stadler
No - mySQL 3 does not support fulltext search in boolean mode.
You can use this with mySQL 3, but you will loose the ability to search for keywords.
@Stadler
No - mySQL 3 does not support fulltext search in boolean mode.
You can use this with mySQL 3, but you will loose the ability to search for keywords.
Uhm, you could use vB's built in postindex. Just add bugid to the post-table, set the threadid to be 0 (or use a 'pseudo-Thread' that is being installed to make reindexing work) and when searching, use something like WHERE bugid <> 0 in the queries.
[Edit:]Oh, and if its too much work for ya I'd volunteer to do the change
Sure I could but then it would be necessary to duplicate vB's search logic (which is not that good IMHO) and to update postindex when a bug(note) is being added or updated.
Using fulltext search in boolean mode makes things a LOT easier
I have some spare time. I could do it ... or I'd just release a how to, to get the search working with MYSQL3, so there would be a MySQL 4-Version and with a bit more hacking a MySQL 3-Version ...