[openbeos] Re: VLC

Mikael Jansson (mailing lists) wrote:
The ticket interface is a little bit overloaded and some fields should be replaced with other things.

Out of curiosity, what do you think is overloaded with it? I believe the ticket system can be fairly easily customized using a template. Should be a lot easier than to completely rewrite the ticket system, don't you think? :)

Well, I'm not completely rewriting the ticket system (and I'm happy that I have not yet really started with coding ;). Collaboa already does much of what Trac does. The biggest problem for me is that Trac is written in Python. Rails makes it many times easier to develop web apps. But okay, here are my Haiku-related issues with Trac (if someone would like to fix them, please step in; I could try to help...):

Cc field:
It must not be possible to remove other users from the list. I'd like to require users to register and then allow for clicking a "Subscribe" button (replacing the Cc field). When someone (*else*) assigns a ticket to you an email notification is sent and you are automatically subscribed. Everyone who modifies/comments-on/creates tickets is automatically subscribed, too.

When I click the "resolve as:" drop-down list I feel interrupted in my work-flow. The list is too long for such a simple action. Nearly all resolutions require a comment (e.g.: why will it not be fixed?), so I would rather remove Resolution and only have these status values:
* Open
* Assigned
* Closed
* Duplicate
* Deleted (add comment on *why*)

Only developers and admins are allowed to create tasks. Users may only create "defect" tickets. This probably requires permissions per ticket type.

Only developers and admins must be assignable to tickets (add permission role).

Milestone, Priority, and Status (and for ticket creation: Assign-To) should only be editable by developers and admins. For normal users the drop-down fields should be hidden. TICKET_APPEND is okay to start with, but non-editable fields should be hidden instead of just disabling them.

When creating tickets, next to the description field there should be a little text (yes, that's easy to fix):
-----
For "defect" reports, please specify:
* how to reproduce
* experienced behavior
* expected behavior
-----

Components should be organized as a tree instead of a flat list.

Severity and Keywords should be removed (it's customizable, so that is not a big problem...).
Hmm, maybe Keywords could replace the component tree, but they should only be editable by developers and admins. For the future, there should be a keyword selector and the values list should adapt to the currently selected component. Guys, what do you think about using keywords? I would not have a problem with that.

Admins should be allowed to save queries for reuse by others (I'd like to disable reports and the wiki) and the default query should list open tickets categorized by milestone.

If you are creating a task or enhancement/wish there should not be a Version field (hide it). I find this extremely confusing! Since only developers can create tasks, this is a minor issue, though.

The wiki is not needed. If the svn plugin does not yet work with remote repositories then we can live without it.

Is MySQL support finally working?
Help would be greatly appreciated! I might have a look at Trac, again. Maybe I can hack something up (I've never used Python, only read some tutorials)...

Bye,
Waldemar

Other related posts: