As of June 1, 2015, the IDE Connector documentation will no longer be maintained by Atlassian. See https://developer.atlassian.com/blog/2015/06/discontinuing-ide-connectors-support/ for more information. We will also be making this documentation available for our open source community here: http://atlassian-docs.bitbucket.org/

10 January 2011

With pleasure, Atlassian presents version 1.3 of the Atlassian Connector for Visual Studio. This plugin allows you to pull in and work with the Atlassian products within Visual Studio. Instead of switching between programs on your desktop, you can see all the information for your project right there in your development environment.

Change in Supported Platforms

As previously announced, the Atlassian Connector for Visual Studio no longer supports a number of platforms. Please see Supported Platforms - Atlassian Connector for Visual Studio for full details.

Don't have the Atlassian Connector for Visual Studio yet?

Download the connector from the Atlassian Plugin Exchange. Follow our installation instructions.

Highlights of this Release:

This is an open source project. You can get the source code from our BitBucket repository.


(blue star) We love your feedback! (blue star)

Please log your issues, requests and votes. They help us decide what needs doing. It is easy to add an issue. If you do not yet have an account, the system will prompt you to create one.

Security-related fixes

As of Version 1.3, the Connector for Visual Studio reuses session cookies while communicating with Applications such as JIRA and Bamboo. This method of communication does a better job of protecting user credentials.

Support for multi-job plans in Bamboo

As of version 2.7, Bamboo is able to have multiple Jobs for its Plans. Each of these jobs produces a separate build log. The connector for Visual Studio is now able to display build logs for all the jobs in the plan.

Complete List of Fixes in this Release

key summary priority status

Data cannot be retrieved due to an unexpected error.

View these issues in Jira
  • No labels