Howdy,

Continuation to my previous inqury, we have finally starting to use Trac 
as primary tool in different projects as bug tracker and such. As being 
lazy I'll ask here, since I think this would interest future readers too.

There is few issues that I would like to solve before doing full launch.

Remote repositories - Box that runs Trac would be Linux + Apache server. 
Repositories reside on Windoze server. Move repos over Linux or some 
nice way to map Win shares to Linux, or usage of remote repositories. I 
prefer native Linux system. All repos are in FSFS format that should be 
just copying all files to new location? I don't have any commit hooks 
and such.

Authenticating users from Active Directory. We're currently using apache 
+ mod_sspi but it sucks. :) Any better way?

Populating Trac users from AD. Since we have all users in AD, It would 
be handy to get "registered" user data from AD? Scripts or plugins for this?

Inter-project references? Since there is need to have few "generic" 
Tracs, how this can be done?

Workflow since we would like to force spesific workflow this would be 
nice - as I understood this will be part of 0.11.

Automation - As much as possible, like automatic ticket closing, ticket 
creation, adding and modifying by email.

Reporting and analysis (statistics) for open/closed tickets, maybe times 
how long they were outstanding and under processing etc.

Work estimation and work done (real working can be gathered from our 
timecard application)

In general - is there articles about (agile) development with help of Trac?

-- 

Jani Tiainen

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" 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/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to