Project management in an established Unity workflow

I'm a software engineer working with an established but very small Unity production environment consisting mostly of a technical artist and a couple of other content people. They use Unity Pro and Asset Server. Git or Subversion, and project management / issue tracking tools are my workflow. Asset Server seems interesting for the artists, but seems to completely lack the features necessary for branching, refactoring and managing shared code assets and issue tracking. The main question, what guidance does the community have for tying in AS (or I guess Team License now) with other project management tools? Are there any project management tools, (Redmine, or even paid tools like Basecamp, Lighthouse, etc...) that have integration for Asset Server?

My first thought is to not use asset server at all now that 3.5 has better VCS integration. But I don't want to completely change their workflow just yet. I really want to not have scripts in the project at all, rather pre build DLLs with the behaviors and have them include those. This way I can maintain the code assets outside of the projects and have better reuse across different projects. This is not a gaming use of Unity by the way, so there are not as many visual elements and large 3d environments filled with assets. It's really hard to find workflow examples of how teams are using Unity.