Hu? JIRA has the same fields as Trac, with the only addition being
enviroment (useful!) and Estimate (could be distracting, could be
useful). I don't see how that is any harder.
Jörn
On Fri, Oct 10, 2008 at 11:33 AM, Volker Mische <[EMAIL PROTECTED]> wrote:
>
> I have to second that. Trac is real
I just recently got my company switched over to JIRA from mantis/bugzilla,
and everybody loves it.
All the data we want, none of the stuff we don't want. Easy to use, easy to
open issues, easy to generate reports, easy to track who's working on what
and what needs to be done.
Can't say enough goo
I have to second that. Trac is really easy to use, JIRA is a monster, it
takes much longer to file a bug in JIRA. It it is more advanced, but is
the ordinary bug reporter that advanced? If the users can't put the
issues into the right tracker (jQuery, jQuery-UI), will they be able to
file the addi
redmine is pretty cool as well, and supports multiple projects, nice
reporting, etc. just something to note.
On Thu, Oct 9, 2008 at 11:50 AM, Jörn Zaefferer
<[EMAIL PROTECTED]> wrote:
> We want to do a test installation first, trying to migrate all users
> and tickets there. Once that is one pla
We want to do a test installation first, trying to migrate all users
and tickets there. Once that is one place, we can look at other
features and test them.
Jörn
On Thu, Oct 9, 2008 at 5:07 PM, Richard D. Worth <[EMAIL PROTECTED]> wrote:
> There's a lot that should be considered for switching to
There's a lot that should be considered for switching to a new issue
tracking system. Among them:
- pre-built reports
- custom reports
- rss feeds
- milestones
- releases
- roadmap
- timeline
I'm not saying this other tool doesn't have these, I'm just saying it's a
big equation.
- Richard
On Th
You have to register as usual. Then creating a new ticket involves
selecting the project, usually that is already preselected based on
the project that you are looking at, and selecting the type, like bug,
enhancement, feature. The second step has fields for Summary,
Priority, Component (subproject
On Oct 7, 6:06 pm, Ariel Flesler <[EMAIL PROTECTED]> wrote:
> I already added a note on our trac, but it seems many people don't
> read it.
The location of the note guarantees that it will never be read by
anyone, especially not someone coming specifically with the task of
creating a new ticket.
Is JIRA really as easy to use as Trac? To me it seems like a beast
and anything that would deter users from posting bugs is a bad thing.
On Oct 8, 4:18 am, "Jörn Zaefferer" <[EMAIL PROTECTED]>
wrote:
> I've recently worked a bit with JIRA, which is used for a lot of
> Apache projects. Usually a
+20!
Bye bye Trac!
--
Ariel Flesler
http://flesler.blogspot.com
On Wed, Oct 8, 2008 at 5:18 AM, Jörn Zaefferer <
[EMAIL PROTECTED]> wrote:
> I've recently worked a bit with JIRA, which is used for a lot of
> Apache projects. Usually a single installation has a dozen or more
> subprojects, so i
I've recently worked a bit with JIRA, which is used for a lot of
Apache projects. Usually a single installation has a dozen or more
subprojects, so its easy to assign a ticket to the right project (its
all in one list). JIRA also has good integration with SVN, usually it
displays changes related to
maybe you could add something like a blacklist which asks the user to
confirm the ticket creation if it contains a term which would normaly
be considered as a part of the UI lib
On 8 Okt., 01:47, "Jaime Ochoa Malagón" <[EMAIL PROTECTED]> wrote:
> Batch close :-),
>
> Share the ticket system with
Batch close :-),
Share the ticket system with UI team, add a checkbox "jquery-ui" or a
set of radio "jquery" "ui-widget1, tabs, ..." (and send the ticket to
the apropiate system or block the send of with a message...)
On Tue, Oct 7, 2008 at 5:06 PM, Ariel Flesler <[EMAIL PROTECTED]> wrote:
>
> H
13 matches
Mail list logo
