I’ve pretty much finished the vB API package I’ve been working on in my Copious Spare Time, based on SirAdrian’s original API code. I may release it on vbulletin.org at some point, but would like to find a brave volunteer to help Beta test it first.

If you use vBulletin for your end user support forums, you may well find this useful. What it does is lets you (the configured ‘unfuddlers’, i.e. staff members with associated Unfuddle logins) easily create new Unfuddle tickets and ticket comments (optionally based on a forum post), and associate existing tickets with forum threads. It supports multiple Unfuddle projects, with optional project default based on forum ID.

Any threads with associated tickets show a table at the top of the ‘showthread’ page, listing the associated tickets. Likewise on the ticket display page, it lists all threads associated with that ticket. Also, on the ‘forumdisplay’ page, any threads with associated tickets get a little ‘bug’ icon next to the thread title.

For vbA CMPS users, there is also a module (“Tickets of Interest”) which lists all threads the logged on member has posted in which have associated tickets. Also a module which lists the last X SVN changesets (revision number and commit comment) for each configured project. An optional template edit also lets you show the latest SVN rev for each project at the top of every vB page.

What I’m aiming at is twofold:

1) To provide a simple way for users to see progress on tickets associated with their support threads, and keep tabs on the SVN change history. I’m also working on a module to list all revision comments between checkpoints, i.e. to act as a “Change History” when you release a new version.

2) To provide a simple way for staff to create and update tickets directly from the support forums. So when a user posts a bug report, a staff member confirms it as a bug, posts a response to the thread, and then can just click a button on the postbit of their reply, creating a new Unfuddle ticket based on that response, and automatically associating the thread with the new ticket. Or if a ticket already exists for that bug, associating the thread with that ticket.

If you are interested, post a reply, and we can arrange to show you round my test site, see this stuff in action, and take it from there.

-- hugh

Joshua,

Thanks for taking the time to walk through the new vBulletin stuff with me. It was indeed good to put a voice to a name.

It’s still very much a work in progress, but you definitely got the idea of what I’m trying to do. I’ve added a few more features in the last few days, like setting Resolutions, and being able to edit (almost) all the fields of a ticket.

I liked your description of the new meta-data feature, and am looking forward to it. You can obviously see why I really want that feature, now you’ve seen what I’m working towards. A tight integration of support threads (and users) in the forums with Unfuddle ticket(s). Coupling our support activities with our development track.

-- hugh

hello im interested about your vb addon please contact me.
heugabel@gmx.net