I am +1 to moving to Jira.
Its a tool, not religion. And its easier to use than bugzilla IMHO.
Stephen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
t: Re: Moving from Bugzilla to JIRA
Henri Yandell wrote:
The following is an example of a Commons like project in Jira. I encourage
anyone who's not used Jira to go have a look at this link and get a feel
for how easy it is to use, compared to the mess that is our bugzilla
installa
Eclipse is one large pile of code and their projects use Bugzilla, it
would be interesting what their install looks like.
Gary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Henri Yandell wrote:
The following is an example of a Commons like project in Jira. I encourage
anyone who's not used Jira to go have a look at this link and get a feel
for how easy it is to use, compared to the mess that is our bugzilla
installation.
http://issues.osjava.org:8080/jira/secure/Brows
+1 on moving from Bugzilla to JIRA.
I've yet to meet an issue tracking system that didn't cause me issues,
but JIRA clearly has more features to support planning, status assessment,
and development. The Foundation already has free access to the product
and source code and is already us
Hola,
>Jira would also allow us to administer our own components and not have
to
>ask infrastructure to add new version id's for component X etc.
Many of us have that ability now: you just need to ask infrastructure
for karma so you get the "edit components" link when you login to
Bugzilla. For
I'm happy to try out an upgrade to Bugzilla before I start campaigning
that Jira is sufficiently better.
Jira's Roadmap and Changelog are the two features that blow Bugzilla away
for me. Attempting to do version management in Bugzilla was so frustrating
that I simply gave up.
Jira would also all
Le 3 sept. 04, à 15:24, David Graham a écrit :
Just because
bugzilla's UI is ugly and JIRA's is pretty is not a valid reason to
switch
to proprietary software in an OSS community.
Well, that's the bone question.
The problem is not aesthetics, the gain in JIRA (for all of us who have
used it) is
D]
>Sent: Friday, September 03, 2004 9:24 AM
>To: Jakarta Commons Developers List
>Subject: Re: Moving from Bugzilla to JIRA
>
>-1 on moving to JIRA. Martin Cooper has indicated there are people in
>infrastructure are willing to do a bugzilla upgrade. Just because
>bugzilla's UI i
Of course we do! I think the matter here is excelence. And
> >> in
> >> my opinion, if there's something actually better and it's avalaible,
> >> why
> >> not? Is that or getting involved on the lesser tool to make it
> better.
> >>
> &
s, 03 de septiembre de 2004 1:59
Para: Jakarta Commons Developers List; Dion Gillard
Asunto: RE: Moving from Bugzilla to JIRA
On principle, I am not in favor of moving /away/ from Bugzilla, an
open-source project, to Jira, a non-open-source project. It feels to
me that this would send a negative m
I'd like to point out that over in Struts, this parallel discussion
came to a rest on the acknowledgement that Struts has such strong
ties to Commons that it doesn't make sense for Struts to change to
JIRA if Commons remains on Bugzilla. Bugs filed against Struts often
resolve to commons compo
I prefer to stick with Bugzilla, for ethical and technical reasons.
Bugzilla is good enough for my needs, I prefer to promote an open source
product, and an upgrade of the version currently deployed on Nagoya is
planned sooner or later.
-1 on migrating [configuration] to JIRA.
Emmanuel Bourg
Di
ommons Developers List
>Subject: RE: Moving from Bugzilla to JIRA
>
>You know my views on JIRA, just search the archives of commons-dev.
>
>+1 move to JIRA
>
>Tim
>
>> -Original Message-
>> From: Henri Yandell [mailto:[EMAIL PROTECTED]
>> Sent
things about JIRA, but not used it much beyond filing
a couple of tickets vs. Maven.
Gary
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 02, 2004 15:40
> To: Jakarta Commons Developers List
> Subject: Moving from Bugzilla to
Is jakarta-commons really a project in JIRA? Jelly has one of its own. You can
only do versions by project, not component, so they probably need to be separate.
I don't know if Apache is running the Enterprise version of JIRA, but it seems
to me that commons is probably a project category... altho
I've found out that the JIRA import process from Bugzilla can only
import a whole project, and not components, and hence all of
jakarta-commons has to go together.
Does anyone still want to stay on Bugzilla?
Do we need a vote for this?
--
http://www.multitask.com.au/people/dion/
---
17 matches
Mail list logo
