We are transitioning our .NET projects to work with SVN, Jira, and VS2008. Does anyone know of a Visual Studio add-on that enables direct interaction with Jira from the IDE? Ideally, it would also support SVN integration (we currently use a different tool for that), though that might be too ambitious. My online searches have mostly led to unrelated mailing list discussions, so any recommendations would be appreciated.
hey all, i checked out a jira integraion plug-in for vs which helped with issue updtaes but wasnt solid on svn. it eased the task handling within the ide. might be worth a look if u can combine it with your svn tool.
I have experimented with the Atlassian Connector for Visual Studio some time ago, and in my experience, it offered a decent level of Jira integration directly within the IDE. It streamlined tasks such as ticket updates and tracking, which brought some cohesion to our workflow. However, while it worked well for managing Jira issues, support for SVN integration was not directly available, so we continued to rely on our existing SVN tools. Overall, the connector significantly reduced context switching between applications for Jira, although handling version control still required a separate approach.
In my experience, although there isn’t a single comprehensive solution that fully integrates Jira and SVN directly within Visual Studio, there are some tools you might find useful. I used a combination of the Jira plugin for Visual Studio with a separate SVN add-in to maintain workflow continuity. The Jira plugin was sufficient for tracking issues and updating tasks directly from the IDE, reducing the need to switch contexts frequently. Unfortunately, the integration of SVN remains limited, so a multi-tool approach seems necessary if you want to manage both systems efficiently.
Based on my experience managing a similar setup, I found that a single all-in-one solution that handles both Jira and SVN integrations in Visual Studio isn’t very common. I opted to use a dedicated Jira add-on which streamlined task tracking and issue updates directly in the IDE. For SVN, I relied on a separate, lightweight integration tool that handled source control operations adequately. Although it wasn’t perfectly unified, this approach minimized context switching and maintained overall workflow efficiency. With a few customizations, the separate tools could be configured to work fairly well together for our development cycle.