El Bruno

Buenas,

Edu 

is a bastard. I was going through it I very well in the MWC2013 with my mobility and Kinect demos for Avanade and I released a complex scenario of integration with VS2012, JIRA, GitHub andTeam Foundation Service that let me touched to the core.

Thus, this scenario I’ve seen usually in companies which uses JIRA as a ticketing system it and then the Dev Team has Visual Studio ALM tools for development and maintenance actions. Then comes an inspired based on vodka who wishes to unite the 2 worlds and the thing is bundled Brown.

JIRA is a great product and is extremely flexible what may seem like a benefit at the beginning, if not planned and controlled, can become an inferno of management that does not tell you. Beware, that this scenario also applies to TFS. Long I recommend thinking several times the fact modify a definition of scope (WI), because it is very tempting and in the long run it can bring us more problems than benefits.

But hey, as I mess with stories that have nothing to do. In both cases, you must use the product sparingly and in that case, it is an excellent choice.

Clear, when these systems are to be integrated among themselves, from the point of TFS first thing in what we think is now in TFS Integration Platform . This integration platform allows us to synchronize information between 2 Data Sources manually, oriented to events, or on the basis of an agenda. OOTB has a series of connectors for TFS for Source Control and defect, and then there are connectors for HP QC, SVN, etc. But for Jira There are no a penalty.

A small search in the Issues of this project in CodePlex leads me to this project, which looks good although it is a bit abandoned. In reality, the project already even exists, so if you want to use TFS Integration Platformas it will be to create a connector for Jira from scratch.

Note:What looks like bad news, really a joy for people like me. I have the perfect excuse to throw me a couple of weeks pulling lines of code hand-in-hand with the Edu.

When I was to see how the API that exposes JIRA for their services, and it was creating a project in VS for a POC, common sense gives me a kick in the head and reminds me of

Surely someone has had this problem, MELON!

And one more time is right. Friends of Atlassian have an extension in its so-called marketplace TFS for Jira. So to download the 30-day trial and see how it works.

Initially seems to have everything that we need in a project, which will be only to see the issue of cost and as hook it on the project.

These are some of its features.

• New! Automatically synchronize changes made to issues and work items between JIRA and TFS
• Viewing TFS check-ins associated with a JIRA issue
• Viewing TFS check-ins associated with a JIRA project
• Viewing history of files associated with a JIRA issue
• Viewing differences of checked in files compared to their previous revisions
• Simple association of TFS check-ins with JIRA issues by means of a check-in comment or check-in note containing the key issue
• Support for multiple TFS servers
• Support for TFS 2010 / 2012 project collections
• Modern, Ajax-based user interface
• support for Microsoft-hosted TFS

To see if I can then comment experiences from mouth of others! ^^

Saludos Finally @ Home

El Bruno