My only beef against TRAC was the developers kept pushing back against core
bugs and the multiple project management was extremely difficult. At the
time we abandoned TRAC we had 23 projects and no way to easily get an
overview of all the tickets. Basically there was no easy way to get a query
for the critical issues across all projects - we wrote a few AIR
applications to accomplish this but it was still too slow to use on a daily
basis. We had several cases of critical tickets getting 'lost' in e-mail
communication and so we needed a solution where this would no longer be an
issue.

I also waited and tried help patch the TRAC connector plug-in to fix the
large packet request - which basically at the time would only let you pull
20 something issues into MyLyn. Here's a comment I made right before I
jumped ship and the link to the bug that was open for over a year
ping-ponging between Eclipse/TRAC developers (
http://nil.checksite.co.uk/index.cfm/2007/10/29/trac-0-11-and-mylyn#cB6F2F475-22FA-885C-7A0FC2378848C3B0).


Now that's not as relevant to Model-Glue because it's a single project,
which TRAC handles pretty well. Just food for thought when looking for some
place to put your 30+ projects. I certainly have no problem with whatever
direction you take the Model-Glue project, just so long as it remains stable
and easy for others to contribute. I'm just sharing my experience, coming
from TRAC looking at different solutions and then choosing the Atlassian
suite for my own company. I am willing to help with the migration in anyway
that I can. I obviously will just be able to help 'the most' with a TRAC ->
JIRA transition.

Here's just a quick list of features that we find very useful and to just
keep in mind when choosing a solution for your own companies issue
management:

   - Multiple Project Management - configure unlimited projects. Get an
   activity stream that shows tickets with comments, attachments, etc across
   all project.
   - Custom Queries - Write your own queries with an auto-complete SQL like
   syntax. Makes finding and organizing large amount of tickets extremely
   useful.
   - Customizable Workflow - Create your own workflow to match your internal
   process. Our tickets go through open and developers close them -> project
   leads review them and then they're cued up for push or further client
   review.
   - MyLyn Plug-in - Manage the ENTIRE workflow within Eclipse. Very mature
   and stable plug-in makes managing all the tickets, getting updates and
   everything without leaving Eclipse.
   - Repository Integration - automatically scans source control
   repositories (in our case SVN) for links to tickets and places them inline
   in the ticket management screens for easy tracking of migration.
   - Granular Security - We can give access to clients to only see the
   progress of tickets and of the project as a whole. You can configure and
   build custom forms for them to enter or view tickets within the interface.
   Hide specific tickets (estimate) that you don't want them to see, etc.
   - Agile Integration - They acquired a great plug-in that makes managing
   stories a breeze. You can drag and drop issues to different sprints, sort
   priorities and monitor burn-down charts automatically.
   - Reporting - Many out of the box plug-ins to view and manage the data in
   your system. Generate reports and understand the burn-down or issues
   overtime /etc.
   - Plug-ins - There are some 140 plug-ins for the latest version of JIRA
   alone. Lots of cool things to sync into time-tracking, and other ways to
   integrate into third-party systems.

Here are some other notable projects (and good examples) of using JIRA:

   - Hibernate -
   http://opensource.atlassian.com/projects/hibernate/secure/Dashboard.jspa
   - Sonatype - https://issues.sonatype.org/secure/Dashboard.jspa
   - Adobe Bug / Issue Management:Flex / Flash Player, etc -
   https://bugs.adobe.com/jira/secure/BrowseProjects.jspa
   - Open Symphony - http://jira.opensymphony.com/secure/Dashboard.jspa


Hope that was helpful!
Roy

-- 
Model-Glue Sites:
Home Page: http://www.model-glue.com
Documentation: http://docs.model-glue.com
Bug Tracker: http://bugs.model-glue.com
Blog: http://www.model-glue.com/blog

You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en

Reply via email to