jQuery Forum

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...)

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

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 a ticket automatically on the ticket.
JIRA gives out free licenses to open-source projects - that may be an
option for us. There are scripts available to migrate from Trac to
JIRA: http://code.google.com/p/trac2jira/
Considering that the UI Trac installation is still offline, this may
be a good time to move.
Jörn

<div dir="ltr">+20!
Bye bye Trac!
--
Ariel Flesler
<a href="http://flesler.blogspot.com">http://flesler.blogspot.com</a>

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 7, 6:06 pm, Ariel Flesler <afles...@gmail.com>

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?), Affects Version(s), Fix Version(s),
Enviroment, Description and Estimate.
Those are eithr pretty close to Trac or quite useful, eg. Enviroment
could include the browser and OS where a bug occured. Estimate is less
useful for a user reporting a bug, though it may be possible to just
hide that, I don't know how much can be customized.
The Affects Version and Fix Versions field seperate between released
and unreleased versions, where each project can have its own versions.
That seems quite useful to me, too.
Jörn

<div dir="ltr">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

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

redmine is pretty cool as well, and supports multiple projects, nice
reporting, etc. just something to note.

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 additional fields in JIRA correctly?
Additional more fine grained information doesn't add value if it isn't
filled out correctly.
Cheers,
Volker
Scott González wrote:
> 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" <joern.zaeffe...@googlemail.com>
> 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 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 a ticket automatically on the ticket.
>>
>> JIRA gives out free licenses to open-source projects - that may be an
>> option for us. There are scripts available to migrate from Trac to
>> JIRA:http://code.google.com/p/trac2jira/
>>
>> Considering that the UI Trac installation is still offline, this may
>> be a good time to move.
>>
>> Jörn
>>
>> On Wed, Oct 8, 2008 at 8:43 AM, markus.staab <markus.st...@redaxo.de> wrote:
>>
>>> 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" <chp...@gmail.com> wrote:
>>>> 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 <afles...@gmail.com>

<div dir="ltr">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 good things about it. Integration with Confluence is nice too. The whole Atlassian suite is pretty nice. I wish we could afford JIRA Studio.
--Erik

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