Complete.Org: Mailing Lists: Archives: freeciv-dev: May 2006:
[Freeciv-Dev] (PR#16811) Issue tracking system for Freeciv
Home

[Freeciv-Dev] (PR#16811) Issue tracking system for Freeciv

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
Subject: [Freeciv-Dev] (PR#16811) Issue tracking system for Freeciv
From: "Kevin Benton" <s1kevin@xxxxxxxxxxx>
Date: Thu, 4 May 2006 13:07:01 -0700
Reply-to: bugs@xxxxxxxxxxx

<URL: http://bugs.freeciv.org/Ticket/Display.html?id=16811 >

> > Why is RT, as configured, a royal pain to use?
> > What is the problem with the basic design of RT?
> 
> From what I've seen of the Freeciv implementation of RT, there are a few
> issues that strike me right away:  There's no basic search versus
> advanced search capability and the searches that I see are rather
> limited in capability.  Also, as-configured, I don't see a way for users
> to sign themselves up for RT access.  RT also lets users see buttons
> they're restricted from clicking on such as changing an issue's status.
>  Bugzilla doesn't allow that.  I could go on, but I think you'll find
> http://bugzilla.mozilla.org/ to be an excellent example of how Bugzilla
> is being used today.

Some other things came to mind while looking at this:

* RT doesn't seem to have a sense of "severity" meaning the customer's
perspective of how bad an issue is.
* RT doesn't seem to have a sense of a target milestone for issues to
help plan what needs to be fixed for a particular release.
* How do I look for issues I've made comments on in RT?
* How do I look for issues that have abc@xxxxxxx in the CC list?
* It seems that bugs get resolved here, but don't go beyond resolved. 
In the installaions I use, we can go to Verified, and Closed.  This is
helpful because an issue can be resolved but not verified, and verified
but not closed (installed and released is one possible definition when
the resolution is "fixed").
* I don't see any way to associate keywords with issues in RT.  Am I
missing something?
* Bugzilla saved searches don't require users to bookmark anything.  RT
does and when the user changes computers, they loose their searches
unless they can carry their bookmarks across.
* RT doesn't appear to have any QA process in it at all.  There are no
QA contacts, nor (as said above) is there a verification process once an
issue is resolved.

I could go on, but I think you get the idea.




[Prev in Thread] Current Thread [Next in Thread]