The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
We're a very small shop with an IT department that just shrunk to below ten people, but the number of people that should be able to write tickets counts in thousands. We're exclusively doing Visual Studio for the foreseeable future.
The switch was made a couple of weeks ago; we used an in-house system (MS Groove workspace) and had a good process workflow that we were not able to completely reproduce with JIRA, mostly because of different mentality.
JIRA is working nicely for end-users; logging work and adding comments is simple and straightforward , and our manager (a good one) is happy with all the reporting and management tools.
One thing is that by default, JIRA will sent TONS of emails; so you have to configure it properly (system and per user).
we are about to integrate Crucible for code review, I did not try it yet, so I cannot comment about that
Really depends on the team, their size and skill-set, the project, etc. Recently I decided to go with SVN for a project, mainly because I need both *Nix and Win support and nobody else where I work has *Nix experience, and I'm not using VS to develop it. Once git gets better Windows support I'll switch over to that.
If I were in a large corporate environment again, with a bunch of MS devs using VS, I'd be tempted to stay with TFS. That unless until MS increases their git support in VS too, in which case TFS goes bye bye along with SVN.
I was 'blissfully' ignorant of so much until I started the new job last Monday. Suddenly everything is cloud. TFS, Visual Studio Online, and Azure. The only 'local' servers my work has come close to are the domain and Exchange.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
I could go on and on, but really it comes down to the business model used. By that I mean the argument for it depends on the business model. It seems however, that whatever the business model is a case can be made for it. It really is some powerful tooling and nothing really competes on its capability for all levels.
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
The interesting thing about software is it can not reproduce, until it can.
TFS has basic issue tracking, but configuring fields and changing allowed statuses requires exporting xml, editing it and importing it.
Each project has a template for how issues are tracked, but changing templates midstream can be a pain, and some features aren't available for all templates. Upgrading major versions of TFS can be a pain, and synchronizing the 5 databases to get clean backups requires a custom script.
The source control portion is better now, and you don't have always be connected to the TFS server without it complaining. However, TFS is lacking things like being able to search for commit messages. The file search will only search by file name not file content.
Branching and merging work just like other systems and I haven't had any issues with any of the basic operations. However, it can support something like a 20 server configuration with multiple database servers, web servers, sharepoint servers, and custom source proxy servers for handling remote offices, so it can definitely scale up to handle something as huge as the windows codebase.