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 [EMAIL PROTECTED] if you have any specific comments about the
ASF instance.


Cheers,

--Jeff


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to