Ticket System

[Jeff Wheeler]

We should implement some sort of ticket system, where we can track forum issues. Like, currently Joppe's footer requests HTTP authentication. Rather than having to IM Kirupa, I would make a ticket that anybody could check, and one of the mods would see it, and hopefully take care of it.

It doesn't have to be complex, but something simple where we can post current issues and comment on them.

Now that I think of it, perhaps even a forum specific to this?

[hl]

AKA Forum Guidelines/Suggestions? The one you're posting in..

[Jeff Wheeler]

No. This is for bigger things… I'm talking about something for small temporary bugs that should be fixed.

[hl]

Well if Kirupa's up to the idea, I'm willing to make a ticket system in PHP. I really need some new stuff to code.

[Jeff Wheeler]

And I'm willing to make it in Django. :P

[hl]

Does MT even support Python?

[kirupa]

You could always use the report post feature also instead of contacting individual mods. A ticket system seems overkill, for in the end, a mod would have to take care of the issue anyway, so why not use existing tools? :evil2:

[hl]

Yeah, I was about to post that too. Additionally, a ticket system would just make for a whole set of new Krilnons bugging Mods' inboxes.

[Jeff Wheeler]

Because, from my experience, mods never read those. Learned that with Kyle. :)

I think some mod said they show up in some odd place that you wouldn't see normally. Do they show up when you browse past the post?

[hl]

Yeah, no one will read tickets either. Do you see any difference whatsoever?

[Jeff Wheeler]

Post reports are tied to specific posts, and nobody can reply. :P

Tickets would be tie to nothing… they could be related to a broken theme, an annoying user, etc… not one post.

[kirupa]

I'll add it to the bottom of my list of things to do then :beam:

(in the meantime, continue to use the Post Reporting feature)

[Jeff Wheeler]

Alright… :P

I guess we'll start coding it, then. ;)