You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Conor MacNeill <co...@cortexebusiness.com.au> on 2004/01/09 11:40:24 UTC
[VOTE] Bug Tracking System
Hi all,
Another infrastructure issue to consider. The ASF is currently installing a
JIRA instance (http://www.atlassian.com/software/jira/). Each ASF project
will need to decide whether it wishes to move to the new system or stay with
BugZilla.
If moving, all current BugZilla issues will be migrated. This one is a fair
way off still as the instance and migration issues are shaken down but I'd
like to get an indication of where people feel we should go.
[ ] +1 Bugzilla sucks - go to Jira
[ ] -1 BugZilla rocks - if it ain't broke, don't fix it.
Let me know.
Conor
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Peter Reilly <pe...@corvil.com>.
Stefan Bodewig wrote:
>On Fri, 9 Jan 2004, Conor MacNeill <co...@cortexebusiness.com.au>
>wrote:
>
>
>
>>If moving, all current BugZilla issues will be migrated.
>>
>>
>
>This is the most important feature to me, otherwise I don't care too
>much. I'm not unhappy with Bugzilla but not thrilled by it either.
>
>
I would agree with Stefan, although I rather like bugzilla.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Jeff Turner <je...@apache.org>.
On Sun, Jan 11, 2004 at 02:40:33PM +0100, Antoine Lévy-Lambert wrote:
...
> Hi Jeff,
>
> I have tried the popular issues link :
> http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10388&report=popular
> from
> the ant's main page :
> http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10388
(it's all disappeared now - we've done the final migration from codehaus
and the jira instance is now live)
> I see an empty frame. Did your data migration procedure import the
> votes ?
No it didn't. I'm very glad you noticed, because it gives me a chance to
fix that before we import any Bugzilla projects.
> I also tried to get my password by email (assuming that you migrated
> the users too) but got no email so far.
The mail server hadn't been configured. It has now.
Thanks again for the feedback.
--Jeff
> Cheers,
>
> Antoine
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Antoine Lévy-Lambert <an...@antbuild.com>.
Jeff Turner wrote:
>On Sat, Jan 10, 2004 at 12:39:11AM +1100, Conor MacNeill wrote:
>
>
>>On Sat, 10 Jan 2004 12:27 am, Stefan Bodewig wrote:
>>
>>
>>>On Fri, 9 Jan 2004, Conor MacNeill <co...@cortexebusiness.com.au>
>>>
>>>wrote:
>>>
>>>
>>>>If moving, all current BugZilla issues will be migrated.
>>>>
>>>>
>>>This is the most important feature to me, otherwise I don't care too
>>>much. I'm not unhappy with Bugzilla but not thrilled by it either.
>>>
>>>
>>>
>>Agreed. I think we should verify that we are happy with the migration
>>before agreeing to any cutover.
>>
>>
>
>FYI, the ASF test JIRA instance is online at:
>
>http://nagoya.apache.org/jira/
>
>I've imported Ant's Bugzilla data so you can see what it's like. Please
>send any comments to jira@apache.org. This data is very likely to be
>trashed over the next few days as the migration proceeds, but we can
>import Bugzilla projects at any time.
>
>
>--Jeff
>
>
>
>>Conor
>>
>>
>>
>
>
>
>
>
Hi Jeff,
I have tried the popular issues link :
http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10388&report=popular
from
the ant's main page :
http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10388
I see an empty frame. Did your data migration procedure import the votes ?
I also tried to get my password by email (assuming that you migrated the
users too) but got no email so far.
Cheers,
Antoine
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Jeff Turner <je...@apache.org>.
On Sat, Jan 10, 2004 at 12:39:11AM +1100, Conor MacNeill wrote:
> On Sat, 10 Jan 2004 12:27 am, Stefan Bodewig wrote:
> > On Fri, 9 Jan 2004, Conor MacNeill <co...@cortexebusiness.com.au>
> >
> > wrote:
> > > If moving, all current BugZilla issues will be migrated.
> >
> > This is the most important feature to me, otherwise I don't care too
> > much. I'm not unhappy with Bugzilla but not thrilled by it either.
> >
>
> Agreed. I think we should verify that we are happy with the migration
> before agreeing to any cutover.
FYI, the ASF test JIRA instance is online at:
http://nagoya.apache.org/jira/
I've imported Ant's Bugzilla data so you can see what it's like. Please
send any comments to jira@apache.org. This data is very likely to be
trashed over the next few days as the migration proceeds, but we can
import Bugzilla projects at any time.
--Jeff
> Conor
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Conor MacNeill <co...@cortexebusiness.com.au>.
On Sat, 10 Jan 2004 12:27 am, Stefan Bodewig wrote:
> On Fri, 9 Jan 2004, Conor MacNeill <co...@cortexebusiness.com.au>
>
> wrote:
> > If moving, all current BugZilla issues will be migrated.
>
> This is the most important feature to me, otherwise I don't care too
> much. I'm not unhappy with Bugzilla but not thrilled by it either.
>
Agreed. I think we should verify that we are happy with the migration before
agreeing to any cutover.
Conor
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Stefan Bodewig <bo...@apache.org>.
On Fri, 9 Jan 2004, Conor MacNeill <co...@cortexebusiness.com.au>
wrote:
> If moving, all current BugZilla issues will be migrated.
This is the most important feature to me, otherwise I don't care too
much. I'm not unhappy with Bugzilla but not thrilled by it either.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Steve Loughran <st...@iseran.com>.
Jeff Turner wrote:
> Hi,
>
> Disclaimer: I work for Atlassian, the company responsible for Jira. I've
> had my Apache hat a good deal longer though.
These all seem reasonable comments; I like your honesty about the
limitations. As nobody has stood up and accused the product of being
outright evil (which I will do do ClearQuest and to a lesser extent
ClearCase(*)). I would like a net api so that apps can do stuff like
present their own UI *if needed*.
>>>[ 1 ] +1 Bugzilla sucks - go to Jira
(*) I dont really view ClearCase as evil. More like a dark and
unforgiving mountain ice route that will destroy you uncaringly if you
get something even slightly wrong. No, it is sourcesafe that it is evil,
primarily though the fact that it gives users the illusion that it
actually keeps your source safe on the sever, when in fact it keeps the
source in a shoe box somewhere on the roof, exposed to the weather and
likely to wash away lines of text in the rain.
>
> On Mon, Jan 12, 2004 at 10:24:44AM +0000, Steve Loughran wrote:
>
>>Conor MacNeill wrote:
>>
>>>Hi all,
>>>
>>>Another infrastructure issue to consider. The ASF is currently installing
>>>a JIRA instance (http://www.atlassian.com/software/jira/). Each ASF
>>>project will need to decide whether it wishes to move to the new system or
>>>stay with BugZilla.
>>>
>>>If moving, all current BugZilla issues will be migrated. This one is a
>>>fair way off still as the instance and migration issues are shaken down
>>>but I'd like to get an indication of where people feel we should go.
>>>
>>>[ ] +1 Bugzilla sucks - go to Jira
>>>[ ] -1 BugZilla rocks - if it ain't broke, don't fix it.
>>>
>>
>>While I have a lot of disrespect for bugzilla; I have had even worse
>>experiences with Rational ClearQuest, so would like to know more about
>>Jira ... has anyone used it? What was the experience?
>
>
> It is generally claimed to have a nicer UI and better overall features.
> Once logged in, you can configure your front page ('dashboard') to
> display only the projects you're interested in, including saved search
> results (eg "New issues this week", "Issues assigned to me", etc). Other
> neat stuff:
>
> - Saved searches can be shared between users, and 'subscribed' to
> (generating a periodic email of results).
>
> - Search results viewable as RSS, allowing neat integration tricks. Eg.
> use <xslt> to generate release notes, or display latest bugs on the
> website: http://xml.apache.org/forrest/forrest-issues.html
>
> - Interaction via email: reply to a change notification email, and your
> reply will appear as a comment in the issue.
>
> - Commit emails mentioning a bug can have their comments appear in the
> mentioned issue.
>
> - Various reports: changelogs, roadmaps, 'popular issues'.
>
> ASF projects like Maven, Jelly, Geronimo, Forrest, etc had been voting
> with their feet, using on codehaus.org's Jira. Hence we've established
> an ASF Jira to accommodate projects' preferences.
>
> There are various public Jira instances you can poke around with to form
> an opinion:
>
> http://jira.atlassian.com/ # Tracks jira bugs; has a test project for experimentation
> http://issues.apache.org/jira/ # Just established - used by Geronimo, Phoenix, Jelly, etc
> http://jira.codehaus.org/ # Various codehaus projects, and Maven
> http://issues.cocoondev.org/ # Forrest :)
> http://jira.opensymphony.com/
> http://opensource.atlassian.com/projects/spring/
> http://opensource.atlassian.com/projects/xdoclet/
> ...
>
>
>>What is there in the way of SOAP or REST programmatic interaction?
>
>
> Jira is IMHO pretty weak at both. There is a SOAP API, but immature and
> rarely used. The URL space isn't that nice (a pet rant of mine):
>
> http://jira.atlassian.com/secure/ViewIssue.jspa?key=JRA-2058
>
> This is getting fixed in the next version of JIRA. Another thing I'm
> personally very keen to see is better interaction-through-email support:
>
> http://jira.atlassian.com/secure/ViewIssue.jspa?key=JRA-2326
>
> On the theory that less intrusive == better,
>
> Please ping jira@apache.org if you have any specific comments about the
> ASF instance.
>
>
> Cheers,
>
> --Jeff
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote:
> Hi,
>
> Disclaimer: I work for Atlassian, the company responsible for Jira. I've
> had my Apache hat a good deal longer though.
I have always said that Bugzilla was fine for me, no need to change.
Then I tried JIRA, and find it generally nicer, but for the use I make
of it, no real big change (heavy users have found it much metter though).
Then Pier said that he will not upgrade Bugzilla as it sucks and he is
damn fed up with it, so now I champion Jira. :-)
(At work I use Scarab because it's free, and it's a pilot program. I'm
sure it will be come a great piece of software, but IMHO ATM it's more
complicated to use, so I still prefer to see Jira here for now)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Jeff Turner <je...@apache.org>.
Hi,
Disclaimer: I work for Atlassian, the company responsible for Jira. I've
had my Apache hat a good deal longer though.
On Mon, Jan 12, 2004 at 10:24:44AM +0000, Steve Loughran wrote:
> Conor MacNeill wrote:
> >Hi all,
> >
> >Another infrastructure issue to consider. The ASF is currently installing
> >a JIRA instance (http://www.atlassian.com/software/jira/). Each ASF
> >project will need to decide whether it wishes to move to the new system or
> >stay with BugZilla.
> >
> >If moving, all current BugZilla issues will be migrated. This one is a
> >fair way off still as the instance and migration issues are shaken down
> >but I'd like to get an indication of where people feel we should go.
> >
> >[ ] +1 Bugzilla sucks - go to Jira
> >[ ] -1 BugZilla rocks - if it ain't broke, don't fix it.
> >
>
> While I have a lot of disrespect for bugzilla; I have had even worse
> experiences with Rational ClearQuest, so would like to know more about
> Jira ... has anyone used it? What was the experience?
It is generally claimed to have a nicer UI and better overall features.
Once logged in, you can configure your front page ('dashboard') to
display only the projects you're interested in, including saved search
results (eg "New issues this week", "Issues assigned to me", etc). Other
neat stuff:
- Saved searches can be shared between users, and 'subscribed' to
(generating a periodic email of results).
- Search results viewable as RSS, allowing neat integration tricks. Eg.
use <xslt> to generate release notes, or display latest bugs on the
website: http://xml.apache.org/forrest/forrest-issues.html
- Interaction via email: reply to a change notification email, and your
reply will appear as a comment in the issue.
- Commit emails mentioning a bug can have their comments appear in the
mentioned issue.
- Various reports: changelogs, roadmaps, 'popular issues'.
ASF projects like Maven, Jelly, Geronimo, Forrest, etc had been voting
with their feet, using on codehaus.org's Jira. Hence we've established
an ASF Jira to accommodate projects' preferences.
There are various public Jira instances you can poke around with to form
an opinion:
http://jira.atlassian.com/ # Tracks jira bugs; has a test project for experimentation
http://issues.apache.org/jira/ # Just established - used by Geronimo, Phoenix, Jelly, etc
http://jira.codehaus.org/ # Various codehaus projects, and Maven
http://issues.cocoondev.org/ # Forrest :)
http://jira.opensymphony.com/
http://opensource.atlassian.com/projects/spring/
http://opensource.atlassian.com/projects/xdoclet/
...
> What is there in the way of SOAP or REST programmatic interaction?
Jira is IMHO pretty weak at both. There is a SOAP API, but immature and
rarely used. The URL space isn't that nice (a pet rant of mine):
http://jira.atlassian.com/secure/ViewIssue.jspa?key=JRA-2058
This is getting fixed in the next version of JIRA. Another thing I'm
personally very keen to see is better interaction-through-email support:
http://jira.atlassian.com/secure/ViewIssue.jspa?key=JRA-2326
On the theory that less intrusive == better,
Please ping jira@apache.org if you have any specific comments about the
ASF instance.
Cheers,
--Jeff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Steve Loughran <st...@iseran.com>.
Conor MacNeill wrote:
> Hi all,
>
> Another infrastructure issue to consider. The ASF is currently installing a
> JIRA instance (http://www.atlassian.com/software/jira/). Each ASF project
> will need to decide whether it wishes to move to the new system or stay with
> BugZilla.
>
> If moving, all current BugZilla issues will be migrated. This one is a fair
> way off still as the instance and migration issues are shaken down but I'd
> like to get an indication of where people feel we should go.
>
> [ ] +1 Bugzilla sucks - go to Jira
> [ ] -1 BugZilla rocks - if it ain't broke, don't fix it.
>
While I have a lot of disrespect for bugzilla; I have had even worse
experiences with Rational ClearQuest, so would like to know more about
Jira ... has anyone used it? What was the experience? What is there in
the way of SOAP or REST programmatic interaction?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
> [X] +1 Bugzilla sucks - go to Jira
> [ ] -1 BugZilla rocks - if it ain't broke, don't fix it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Steve Loughran <st...@iseran.com>.
Gus Heck wrote:
> My non-non commiter vote:
>
>> [ ] +1 Bugzilla sucks - go to Jira
>> [x] -1 BugZilla rocks - if it ain't broke, don't fix it.
>>
>>
>>
Oh, this is good.
I agree with you; bug entry is critical.
When we used Rational ClearQuest, I once spent 30 minutes filling in
some inordinately complex form describing a hard to replicate problem,
with all the test data, etc.
Then I hit submit, and got
"session timed out"
needless to say, I was not happy - we moved to bugzilla shortly
thereafter, showing that usability comes above seamless integration with
SCM tools.
> Doesn't it figure. I read a similar commons thread, and wrote a long
> email about why I think bugzilla is friendlier to the novice user than
> both JIRA and Scarab then I come here and see the same issue. Apparently
> I should have wrote it here... That is what I get for reading the other
> mail first :) One of the biggest strengths of Ant (and any OSS project)
> is the user feedback from both experienced and novice users... Here is
> most of what I posted (minus a question that has already been answered
> there), which I think we should consider here too. (I don't beleive it
> is likely to have hit the archives yet or I would link it).
>
> I sometimes think that there is an aspect of the ASF bug tracking
> systems that gets forgotten... How easy it is to learn to use them. As a
> contributer to Ant, and an operator of my own bugzilla, I have been very
> satisfied with bugzilla in this repsect. The first time I ever used
> bugzilla I had no trouble figuring out how to do a query, or fill in a
> bug form. The query form seemed a bit disorganized, but there were lots
> of explanatory links and with a little looking I found the submit button
> without too much trouble. I have not once had to explain details of how
> to use bugzilla to users of my bugzilla, nor have I recieved complaints
> about it. Some of the users are introductory programming students who
> have never used any bug tracker before.
>
> In contrast, I don't like scarab. I have several times found issues in
> OJB (relating to JDO implementations), but they use Scarab. Scarab I
> regret to say is quite difficult to use (at least if you don't already
> know how to use it, or maybe only if you are used to using bugzilla, I
> don't know which). It entirely fails to document itself clearly.
> Bugzilla has explanitory links all over it's bug creation and query
> forms, which is something I beleive to be critical to a bug tracking
> system that will be accessed by users who are not already familiar with
> it. I have several times tried to use Scarab, and each time it has
> failed, or it has eaten all my plain text formatting by coalescing all
> the whtiespace (that makes stack traces really fun to read), or whatnot.
> I am sure it is user error on my part, but so far I really haven't had
> time to find out where to read up on how to properly use Scarab. Another
> annoyance is that after you sign up for an account with scarab it tells
> you you must "request" membership in a project, which seems to imply
> that you might be rejected. Really not a very welcoming start.
>
> The systems used at apache should (IMHO) be transparent, user friendly
> and self explanitory. If they want users to report bugs in their
> software, it should be easy to learn the system. The current result with
> Scarab and me, is if I see that a project uses scarab, I only report
> bugs on their mailing list. I suppose if I decide I want to become a
> direct contriubuter to a project that uses Scarab, or I have some free
> time and think of it, I will take the time do the research to figure out
> how to enter bugs properly in Scarab.
>
> So I wrote the above mostly based on the gut reaction, oh no not another
> bug system to fight with...
>
> After looking at Jelly's JIRA as linked from their project pages
> (http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10012), it
> is clear that there are some nice features, it looks nicer than both
> bugzilla and scarab and is and friendlier than scarab, but I do see one
> major usability glitch. Nowhere did I see a link for Entering a bug.
> This is the main reason people come to a bug database. How can there not
> be a link on the front page for it!?!? I have a strong suspeicion that
> such a link would have appeared had I created an account and logged in,
> but there was no link for that either... just a log in link. (now I
> think it is vairly likely if I followed the log in link it would
> eventually get me to an account creation link, but....) Only my existing
> knowledge of how web apps and bug trackers tend to work tells me that.
> Nothing on the page helps you enter a bug. (unless I am blind or stupid,
> both of which happen occasionally). It could use more explanitory links
> too, but at least there was a help link (once I saw the really tiny
> bubble thing in the upper right) that led to a detailed manual (though
> that manual didn't have a "Enter a bug" section). I didn't have time to
> browse the manual deeply, but this is still inferior to links on the
> issue entry page, because the user must leave the page, and search the
> manual for the item they don't understand, rather than being taken
> directly to the item. It's hypertext man, take advantage of that!
>
> The entry page is is a stark contrast to bugzilla where you are
> immediately provided with links to do each of the main tasks (quick
> search, detailed query, enter bug, get summaries, log in, create
> account). Whatever reason someone came to a bugzilla front page, (other
> than by accident) the link is there where they can't miss it.
>
> So my order of preference for bug tracking from a "support the novice
> user" perspective is:
>
> Bugzilla
> JIRA
> Scarab
>
> Just my $0.02 worth (I don't get much per word do I?),
>
> -Gus
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Gus Heck <gu...@cognition.olin.edu>.
My non-non commiter vote:
>[ ] +1 Bugzilla sucks - go to Jira
>[x] -1 BugZilla rocks - if it ain't broke, don't fix it.
>
>
>
Doesn't it figure. I read a similar commons thread, and wrote a long
email about why I think bugzilla is friendlier to the novice user than
both JIRA and Scarab then I come here and see the same issue. Apparently
I should have wrote it here... That is what I get for reading the other
mail first :) One of the biggest strengths of Ant (and any OSS project)
is the user feedback from both experienced and novice users... Here is
most of what I posted (minus a question that has already been answered
there), which I think we should consider here too. (I don't beleive it
is likely to have hit the archives yet or I would link it).
I sometimes think that there is an aspect of the ASF bug tracking
systems that gets forgotten... How easy it is to learn to use them. As a
contributer to Ant, and an operator of my own bugzilla, I have been very
satisfied with bugzilla in this repsect. The first time I ever used
bugzilla I had no trouble figuring out how to do a query, or fill in a
bug form. The query form seemed a bit disorganized, but there were lots
of explanatory links and with a little looking I found the submit button
without too much trouble. I have not once had to explain details of how
to use bugzilla to users of my bugzilla, nor have I recieved complaints
about it. Some of the users are introductory programming students who
have never used any bug tracker before.
In contrast, I don't like scarab. I have several times found issues in
OJB (relating to JDO implementations), but they use Scarab. Scarab I
regret to say is quite difficult to use (at least if you don't already
know how to use it, or maybe only if you are used to using bugzilla, I
don't know which). It entirely fails to document itself clearly.
Bugzilla has explanitory links all over it's bug creation and query
forms, which is something I beleive to be critical to a bug tracking
system that will be accessed by users who are not already familiar with
it. I have several times tried to use Scarab, and each time it has
failed, or it has eaten all my plain text formatting by coalescing all
the whtiespace (that makes stack traces really fun to read), or whatnot.
I am sure it is user error on my part, but so far I really haven't had
time to find out where to read up on how to properly use Scarab. Another
annoyance is that after you sign up for an account with scarab it tells
you you must "request" membership in a project, which seems to imply
that you might be rejected. Really not a very welcoming start.
The systems used at apache should (IMHO) be transparent, user friendly
and self explanitory. If they want users to report bugs in their
software, it should be easy to learn the system. The current result with
Scarab and me, is if I see that a project uses scarab, I only report
bugs on their mailing list. I suppose if I decide I want to become a
direct contriubuter to a project that uses Scarab, or I have some free
time and think of it, I will take the time do the research to figure out
how to enter bugs properly in Scarab.
So I wrote the above mostly based on the gut reaction, oh no not another
bug system to fight with...
After looking at Jelly's JIRA as linked from their project pages
(http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10012), it
is clear that there are some nice features, it looks nicer than both
bugzilla and scarab and is and friendlier than scarab, but I do see one
major usability glitch. Nowhere did I see a link for Entering a bug.
This is the main reason people come to a bug database. How can there not
be a link on the front page for it!?!? I have a strong suspeicion that
such a link would have appeared had I created an account and logged in,
but there was no link for that either... just a log in link. (now I
think it is vairly likely if I followed the log in link it would
eventually get me to an account creation link, but....) Only my existing
knowledge of how web apps and bug trackers tend to work tells me that.
Nothing on the page helps you enter a bug. (unless I am blind or stupid,
both of which happen occasionally). It could use more explanitory links
too, but at least there was a help link (once I saw the really tiny
bubble thing in the upper right) that led to a detailed manual (though
that manual didn't have a "Enter a bug" section). I didn't have time to
browse the manual deeply, but this is still inferior to links on the
issue entry page, because the user must leave the page, and search the
manual for the item they don't understand, rather than being taken
directly to the item. It's hypertext man, take advantage of that!
The entry page is is a stark contrast to bugzilla where you are
immediately provided with links to do each of the main tasks (quick
search, detailed query, enter bug, get summaries, log in, create
account). Whatever reason someone came to a bugzilla front page, (other
than by accident) the link is there where they can't miss it.
So my order of preference for bug tracking from a "support the novice
user" perspective is:
Bugzilla
JIRA
Scarab
Just my $0.02 worth (I don't get much per word do I?),
-Gus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Steve Loughran <st...@iseran.com>.
Antoine Lévy-Lambert wrote:
>>
>>
>> I have just had a look at the JIRA web site, and their product looks
>> nicer than bugzilla.
>>
>>
> So
>
> [x] +1 Bugzilla sucks - go to Jira
> [ ] -1 BugZilla rocks - if it ain't broke, don't fix it.
>
> I hope that the other Apache projects will be positive to migrate to
> JIRA, because there is sometimes a certain synergy in having all the
> Apache projects in the same bug tracking system,
> for instance you can reassign to the tomcat colleagues a problem with
> jspc if you think that it is not ant's fault, ...
>
IMO the W3C and Sun workstations should also be on the same system. But
really this calls for a federated defect cross assignment network (built
on something like RDF perhaps)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Bug Tracking System
Posted by Antoine Lévy-Lambert <an...@antbuild.com>.
>
>
>I have just had a look at the JIRA web site, and their product looks nicer than bugzilla.
>
>
So
[x] +1 Bugzilla sucks - go to Jira
[ ] -1 BugZilla rocks - if it ain't broke, don't fix it.
I hope that the other Apache projects will be positive to migrate to
JIRA, because there is sometimes a certain synergy in having all the
Apache projects in the same bug tracking system,
for instance you can reassign to the tomcat colleagues a problem with
jspc if you think that it is not ant's fault, ...
Cheers,
Antoine
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org