Atlassian IDE Connector 3.0

By Jens Schumacher, Product Manager
Bamboo, Bitbucket, FishEye, Crucible, Dev Tools
On February 9, 2011

We started the open source Atlassian IDE Connector project a few years ago with the goal of providing developers with a faster and more convenient way to interact with Atlassian applications. Thousands of downloads and a few years later, the Connectors provide access to many of the features available within the web applications, but the rest of the world did not stand still. The web and our products have evolved to the point that they eclipsed (no pun intended) the user-experience within the IDE and continue to provide more and more features that proved to be challenging to implement across a number of IDE’s with UI frameworks tailored towards editing code. In the end, we are just duplicating functionality that is already available, and often easier to use, via an excellent web user interface.

With this in mind, we took a hard look at the feature set of the Connectors, the statistics we’ve gathered over the past year, and the effort we’ve spent on maintaining these features. We came to the conclusion that it is no longer feasible spending the time of 6 full-time developers duplicating new and maintaining existing features in a different environment. Instead we want to focus our energy on features that enhance the experience of our products and provide additional value, not simply copy existing functionality. Examples of this are the JIRA time-tracking, context tracking and Bamboo notifications.

Atlassian IDE Connector 3.0

Version 3.0 of the Atlassian Connector for Eclipse and IntelliJ IDEA has limited support for Fisheye and Crucible. Existing JIRA features as well as most of the Bamboo functionality have been maintained.

What exactly is changing?

Crucible reviews and some FishEye features have been removed in this version of the Connector. In the Atlassian Connector for Eclipse and IntelliJ IDEA you will no longer be able to:

Create Reviews
View Reviews
Perform Reviews
Open files in FishEye

Available Features

However, we realised that some tasks are made a lot easier by having a useful but lightweight integration. The great feedback we’ve gotten so far encouraged us to not only keep, but improve a couple of integration points between the IDE and Fisheye and Crucible. You will still be able to:

Direct click-through from FishEye to files in the IDE for both Atlassian Connector for Eclipse and IntelliJ IDEA
Create Pre-Commit Reviews (IntelliJ IDEA only, depending on the interest we may put this feature into the Atlassian Connector for Eclipse)

Please note that all of the JIRA functionality is staying in the Atlassian IDE Connectors.

You can see a full list of changes and features in the IDE Connector Release Notes (“Eclipse”:http://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+for+Eclipse+-+v3.0+Release+Notes /

“IDEA”:http://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+for+IntelliJ+IDEA+-+v3.0+Release+Notes)

What about the older version of the Atlassian IDE Connector?

The last version of the Connectors with full Crucible and Fisheye support are:

Atlassian Connector for Eclipse 2.3
Atlassian Connector for IntelliJ IDEA 2.4.2

You will still be able to download these versions of the Connectors, but Atlassian will not maintain version 2.x going forward. The good news is that Atlassian IDE Connectors are open source and we have just made it a whole lot easier for you to contribute by hosting the Atlassian IDE Connectors on BitBucket. Please feel free to fork the Eclipse or IDEA repository and contribute to the project.

What if I have questions?

Please feel free to get in touch with us. You can email me directly under: jens at atlassian dot com

Atlassian Stash - Simple, social & secure enterprise Git management »

We're hiring. A lot. Heaps. Hella. Mucho. Developers, Support Engineers and more »

Comments (65)

Where can I download the 2.3 connectors for Fisheye? Just upgraded to 3.0.0 and we’ve lost our “right click” context menu to get straight to Fisheye from eclipse.
Without it, it just means it’s more difficult to get to Fisheye – (so developers less likely to use it).

By Colin Jones on February 10, 2011 / Reply
Why was the Crucible integration removed?

By Bernard on February 10, 2011 / Reply
It would be nice if you were to have posted what other options are available for your customers who needed these features you no longer support … It pretty much just leaves us hanging after we have invested so much time and money into your product which was suppose to do what you now say you will not be supporting.
Your posting is positive for your company but does not give those of us who needed this functionality for our day to day use of Crucible (even with the large amount of bugs it had in the 2.4.x version). I guess now we can spend our time finding a replacement for Crucible. Thanks a lot….

By Lex Frost on February 10, 2011 / Reply
It’s sad to hear that crucible is no longer supported by Connector. The “I” in IDE is for “Integrated”, and unfortunately there is no integration anymore…

By Anonymous on February 11, 2011 / Reply
Have you guys considered developers opinion before making this decision? As a developer I want to use all these from IDE itself. Why do I need to go to web interface for reviews? My whole team got disappointed with this news. Either we will stick to old connector or move to Jupiter for reviews!

By Hari on February 11, 2011 / Reply
I really liked the pre-commit feature of the plugin – the website is more clicks, nvaigation to set up reviews – really hope the eclipse plugin can be brought back

By Pradeep on February 11, 2011 / Reply
Interesting. My first experience of a Crucible review was not good in the browser and I was thankful of having the Eclipse connector to fall back on.

By Neale Upstone on February 14, 2011 / Reply
BOO! The feature set of the Atlassian Connector for IntelliJ is one of the major reasons we chose Atlassian toolsets for our development. The ability to perform Crucible reviews in the IDE using the built-in familiar functionality of the IDE is, in my opinion, a killer feature. In our experience the web interface of Crucible (as part of JIRA Studio) is slow and clunky compared to using our local installation of IntelliJ with the Atlassian Connector.
I can only hope that you reconsider this strategic move.

By Matt on February 14, 2011 / Reply
Keep pre-commit reviews in intellij – a real time saver. Introduce to Eclipse and Visual Studio – it would help a lot.

By Steve on February 16, 2011 / Reply
Unfortunate on the removal of these features. You could potentially leave the post commit review creation, as that helps the developer workflow. you should survey your customers before removing features folks have come to depend on.

By Trevor Samaroo on February 17, 2011 / Reply
REMOVING the crucible functionality?? Why would you do that? The greatest feature of the plugin was the ability to use the native file compare tools in eclipse and the IDE click-through to navigate code. What was the rationale behind cutting back on this functionality? How else can you create pre-commit reviews (not a patch)?

By Tom Schober on February 17, 2011 / Reply
The removable of the ability to create reviews from the IDE is a huge hole. Doing pre-commit reviews is a no-go for my group right now. They do not want to go through the many painful steps of creating patch reviews.

By Tom on February 18, 2011 / Reply
Disappointing…, IDE integration was the main selling points of Crucible.
Removing it leaves a messy/clunky workflow for developers.
Our investment in Atlassian products was primarily around their integration with each other and with the IDE.
Please reconsider this decision.

By Dave on February 23, 2011 / Reply
I’d like to add my voice to those arguing to put pre-commit reviews back into the Eclipse version. By far the two things I used the connector for the most was team -> create review and team -> add to active review. I find the process of creating patches a real pain on the Eclipse side and the submission of updated files to an active review a real pain on the Crucible side.

By Henry Berg on February 23, 2011 / Reply
You can download version 2.3.0 of the Atlassian IDE Connector here (seems to be suitable for Eclipse 3.4-3.6):
http://update.atlassian.com/atlassian-eclipse-plugin/2.3.0/e3.5

By Sebastian Bärhausen on February 25, 2011 / Reply
What were you thinking!? I expected better from Atlassian. This is probably the poorest product decision I have ever seen. Better reverse this decision fast.

By Justin Petersen on March 1, 2011 / Reply
The company I work for purchased a Crucible license ONLY because of the IDE integration. The web gui is most certainly not “excellent”: it’s ad-hoc, over-complicated and generally very awkward to use. Even if it were excellent, the context switch would still be a problem.
Software developers are busy people doing work that requires intense focus and concentration. They hardly have time for code reviews at all: the process must be fully integrated to be of any use.
As for bragging about the fact that the plugins are open-source — great, now I can spend my spare-time doing Atlassian’s job for them.

By Anonymous on March 3, 2011 / Reply
Not sure why it was an all or nothing decision. I agree you don’t need to duplicate all the capability in the IDE, but there is a smaller set of high use integrations that would likely satisfy 80% and then defer to the web interface for the rest.

By bob swift on March 3, 2011 / Reply
Odd choice. We justified the decision to buy Crucible primarily based on its IDE integration.
I doubt we will renew our support license without it.

By Robert on March 3, 2011 / Reply
The IDE integration is probably the one thing that sets this product suit apart from its competition and the only reason I even looked at it in the first place (There are in fact free tools that are easier to use). What exactly is the reasoning behind this?

By Dan on March 4, 2011 / Reply
Totally disappointing. Doing Crucible reviews in the IDE is sooooo much better than using the web interface. Switching back to 2.3.0 to get the integrated review capabilities back…
Please reconsider.

By Torben Knerr on March 15, 2011 / Reply
This is disappointing news. I was planning to purchase Crucible for our team, partly because of the ability to conduct reviews within Idea.
Will be rethinking this decision now.

By Phil Nash on March 17, 2011 / Reply
Another thing to consider is that most time spent on a review is done reading code. What better place to do that than the most familiar environment of your IDE? Here you have great code analysis tools available, and most importantly – code inspections (in IDEA). I would have thought it would be a great deal more difficult having to do the code review from a browser, but reading the code in the IDE… I always thought of this as Crucible’s killer feature.
We only require a small set of features from the IDE. Even if it was just being able to annotate the code with review comments, that would mean the vast amount work could still be done without having to context switch with a browser page…

By Kieron Wilkinson on March 18, 2011 / Reply
Dear Atlassian,
You really are kidding right. After years of my struggling to get our Northrop Grumman installation to acquire Crucible, we just buy Crucible and then you yank the carpet from under our feet. Yes, we really resent this!!!
How do we get the old version? And NO the web interface is NOT adequate!
Sincerely,
Charles W. Hammes

By Charles Hammes on March 21, 2011 / Reply
I cannot believe, what I read here? No more integration/support for crucible? That was the central argument for using Crucible because of the integration in Eclipse and we bought lisences for Crucible and JIRA. But without that, there is no benefit of using crucible any more, and the use of JIRA must be also reconsidered, because there are other tools with a nice integration, which will fit much better.
This is really very disappointing…

By Ulrich Cech on March 22, 2011 / Reply
You can find instructions on how to install previous versions of the Connectors in our documentation under:
IDEA: http://confluence.atlassian.com/display/IDEPLUGIN/Installing+the+IntelliJ+Connector
Eclipse: http://confluence.atlassian.com/display/IDEPLUGIN/Installing+the+Eclipse+Connector
Note that older versions of the Connector are not supported by Atlassian.

By Jens Schumacher on March 22, 2011 / Reply
This blows..
working with reviews from within idea was one of the best thing by switching to crucible. Please consider bringing the feature back.

By Eirik on March 30, 2011 / Reply
This is unfortunate. As a fairly new user of Crucible, I hoped I could use this plug-in to ease my interaction with it. Because the web GUI is a pain to use. At least, if focus on the interface is prioritized, this is good. I doubt though you will achieve what an IDE does best: code navigation, code analysis, syntax comprehesion, etc.

By Jimmy Royer on March 30, 2011 / Reply
We have just invested in a whole load of Atlassian tools, partly on the back of the integration with Eclipse.
We really need this integration – we love it and to have it pulled like this is unacceptable.
Atlassian says that its values include “Don’t #@!% the customer” – to quote: When we make internal decisions we ask ourselves “how will this affect our customers?” If the answer is that it would ‘screw’ them, or make life more difficult, then we need to find a better way. We want the customer to respect us in the morning.
We are not happy – please reconsider and put this excellent functionality back in.. pulling it like this leaves us nowhere to go and telling your customers to stick with an old unsupported version is really not an option.

By David on April 1, 2011 / Reply
David,
It took as a good 6 month to make this call and we’ve evaluated a whole bunch of different options that wouldn’t “#@!% the customer”. As I’ve highlighted in the post above, we believe that although it will hurt a little at first, in the end we will be able to provide a better product to our customers by focusing our efforts.
I would be interested to hear which of the removed features you consider “excellent functionality” and what an ideal workflow would look like in your case. Please feel free to get in touch with me to discuss this further.

By Jens Schumacher on April 3, 2011 / Reply
- Hi Jens,
  
  the most useful thing in the Crucible integration is the ability to create reviews from (pre-)commits. The web interface for doing this is ok, but far less handy than IDE integration. Sincerely, it takes quite some more time.
  
  Second, it’s very useful to be able to apply code review changes in the IDE.
  
  Please consider to add at least this basic functionality back to IJ and Eclipse. Without it, I don’t think my company will renew the Crucible license.
  
  Regards,
  Soren
  
  By Soren on February 20, 2012
OK, so paraphrasing your words above: “it was too much work to bother so we decided to dump it. Sucks to be you, you’ll get over it.”
I will remember this every day that I have to toggle between the IDE and the freaking web UI, remembering how smooth and easy things were before you decided I didn’t need smooth and easy in my already challenging workday.
You have completely #@!%’ed this customer…

By Jared Rypka-Hauer on April 14, 2011 / Reply
Corollary to my previous comment:
You want to know what an “ideal workflow” is in my world?
It starts with having all my code and repository connections in one place… Eclipse. I use various plugins for XML, Java, ColdFusion, JavaScript and so on. Open/edit/save/test/commit… within the familiar UI of my IDE.
I make heavy use of the JIRA connector’s integration with the IDE and Subclipse, as well as task contexts (which is also horribly screwed in the new version, btw – that’s another conversation). When I commit, I commit to a ticket, and I include the context with the ticket.
So once I’ve opened/edited/saved/tested/comitted my files, it’s time for a review. I USED to be able to, using the same familiar UI in my IDE, create a review, or participate in the reviews created by other developers. There was no mental transition from one UI to another, no switching from one app to another… the code looked the same and was all in the same views for accessing it.
And since I exclusively use the IDE to interact with the JIRA repo I NEVER logged into an Atlassian web UI. Until now anyway. EVERYTHING I needed to do I could do from one context. And since the tools all came from one vendor, everything was very familiar and consistent. All that consistency and centrality made my IDE a very powerful tool and the Atlassian suite a very powerful environment.
Let me put it a different way: Context switching is an expensive operation, in code or in my head. Having to interrupt my work-flow to toggle between _completely_ different code-related environments has made for a far worse experience than any updates or enhancements to the web UI could ever make up for. It costs me time, stress and frustration.
I am very, very angry about this guys… it steams me every time I have to f**k around with it.

By Jared Rypka-Hauer on April 14, 2011 / Reply
Dear Atlassian,
We like your products, that’s why we are all commenting on this page. We use your products throughout our development lifecycles. Please note by the unanimous nature of the above comments, in this instance, you may have made a bad decision.
I am involved in defining the development standards for a multinational bank. We have been recommending Atlassian products – in part, due to the excellent ide integration. This is now a negative point for selecting your tools as part of our bank-wide standard toolset.
Regards,
Nathan

By Nathan Coast on April 15, 2011 / Reply
Can u give us feedback what´s the roadmap for the eclipse ide connector ? Will you reintegrate crucible ?

By Andre Frintrop on April 27, 2011 / Reply
Hello Atlassian-Team,
I was responsible for choosing the Atlassian-Tools in our company because of the very good integration in Eclipse, which is our primary development environment. We use JIRA and Crucible, and apart from the missing functionality in Cricible to update changed class-files, the tool was of great value for use.
But without the integration in Eclipse, Crucible is no longer a valuable tool for use. This is real disappointing, because this is a fundamental wrong decision. The great value lies in the integration in our IDE, everything is in one place, we don’t have to switch applications and so on. I can agree totally to Jared Rypka-Hauer’s post, he bring’s it to the point!
The statement, that it would “hurt at the beginning but results in a better product”, is totally wrong, because it would never be as useful as before because of the missing integration… nice and close integration, this is the key of success.
Please integrate Crucible back to the connector, otherwise we will not see any further value in using crucible any longer…

By Ulrich Cech on April 28, 2011 / Reply
Hi Atlassian-Team,
Please carefully re-evaluate the key selling points of your products.
IDE connector is not duplication. It’s a MUST have, value-added feature.
I would have chosen SmartBear CodeCollaborator/Reviewer instead of Crucible-FishEye some months ago if I know that there will be no support for IDE review. My development team will get mad about this.
Now we are using v2.3 for this feature. And I’m considering a switch since Crucible doesn’t worth the $ without it.
Anyway it’s your decision and the number says it all. Keep going that way and look at your sales.
I hope you guys can post your product roadmap soon.

By LPTan on May 8, 2011 / Reply
Just to add my voice to the din above…
In my opinion the ability to perform code reviews (post commit) in the idea is the most useful and compelling feature of the atlassian connector. I have my browser open all day and can perform JIRA and Bamboo tasks there just as well as in my IDE. But performing reviews in the browser is no good. As a previous commenter mentioned, even if the web UI was excellent, it’s still not good enough. I need the entire file I’m reviewing in the context of my IDE where I can easily browse to other related files as necessary, see the code diff marks in the IDE for this review and view and post comments in-line. This is the easiest and most intuitive way to perform code reviews. And if performing code review isn’t easy – people don’t do them. Sure I can still tell crucible in the browser to open the file in my IDE, but I don’t get the diff marks and I can’t view or add comments, so it’s nearly useless. Myself and several other on my team still open Intellij 9 with the old version of the connector just to do code reviews. That’s how important this feature is. Please bring it back soon!

By Steve Burrows on May 16, 2011 / Reply
Jared and others sum up my opinion. I will be honest and say that Atlassian’s reply annoyed me so much I could not be bothered to respond.
I run the software department for a branch of a major defence contractor – we chose Atlassian tools over the ‘obvious’ alternatives because I knew my developers would love them – they could do everything (pretty much) from one place. You ask about workflow – well, how about my devs being able to navigate the code base from a tools which is designed to do this (Eclipse) when reviewing a change or new feature?
All this functionality existed when we evaluated your products – and now it is being taken away. How can any customer regard that as a ‘good thing’?
I will echo others’ comments here – you have made the wrong decision, no doubt about it. I really hope you will reconsider as bluster aside, I am honestly starting to wonder whether we made the wrong call in picking Atlassian.

By David on May 19, 2011 / Reply
Hi,
Crucible code review from browser ? It does not work that way!
Everyone in our dev. team is using Eclipse while doing code reviews – then they go back to the Crucible Web UI (does not even work in IE! ) and enter comments again (again ! – because they will come up with questions/comments while working in Eclipse, but to enter the text, they have to move to a different software – so it is almost like adding comments again! ).
When we rolled out the Crucible two months back, I tried to install Atlassian IDE Connector for Eclipse. Only reason I would need IDE integration is for code reviews. Did not find it there. Impression I got was, folks at Atlassian must be working on it, should check it out after couple of months. Only today, when I was desperately trying to find out why there is no news about Crucible -Eclipse integration, did I find this much hidden piece of information! Only when I had more time available to read more carefully, I realized that the support for Crucible has been ‘discontinued’!
Atlassian – please save your product and reputation – make the information about IDE Connector 2.3 being available for work with Crucible more prominent !

By Samir J. on May 30, 2011 / Reply
In-browser Crucible is useless because of no code navigation. It makes it no-go for our teams.

By Arseny on October 27, 2011 / Reply
Guys, you “Post comment” deletes entered text when you click the field (Firefox) – it is unbelievable bug

By Arseny on October 27, 2011 / Reply
Atlassian, I have to say this change in direction is disappointing. There are many competitors to crucible, but none of them come close to what y’all *used* to have in terms of IDE support. I think your Intellij support sets crucible apart. When I do code reviews with my team, we actually open both the browser *and* our IDE so we can do all the IDE code navigation, as well as look at code coverage from clover. I think either you have to make crucible in the browser have all the IDE code navigation tricks, or have your IDE plugins just add in the commenting features.

By Andrew on October 29, 2011 / Reply
got nothing meaningful to add that others have not already said… this move blows simple as, can see the refocus side of things but in reality you are screwing the customer in a gnome “we know how you *should* work” kinda way

By paul on October 29, 2011 / Reply
Hello,

we are currently in the process of migrating our development to JIRA and Bamboo.
So we are very disappointed that you lower your support of the Eclipse integration.

How much of these previously assigned 6 full-time resources are left? For Eclipse,
most of the framework code is already provided by the Mylyn top-level project. Please
continue to work with these guys!

Thanks, Jörg

By Jörg Thönnes on November 15, 2011 / Reply
Well, this is disappointing! We are in the process of evaluating Crucible and have had enough dislike that we have been debating which product to use. When I found that there was an IntelliJ plug-in, I told my team that we may have the killer feature that will make Crucible the winner. After trying to get it to work, I stumbled across this post and was pretty pissed off. I don’t recall the “Atlassian Connector for IntelliJ IDEA” pointing out ANYWHERE that it does nothing other than allow you to open files in FishEye/IntelliJ from the other side.

I could understand not maintaining a full featured plug-in, but I should be able to do the basics such as creating a review, stepping through a review and adding comments.

Decision made. If you are a company that freely yanks useful features that people have come to rely on like this with no real warning, then we’ll go somewhere else.

Weak. Fail. You suck. I’m taking my ball and going home.

By Ken on January 26, 2012 / Reply
For our company, crucible was the *only* feature needed in the IDE connector. Who the heck cares about jira and bamboo integration? The web is good enough for those products. Reviewing through the IDE is the only worthwhile feature of the connector. Very disappointed. Going to look for alternatives.

By Jake on February 8, 2012 / Reply
I am in the process of setting up an evaluation FE/CR installation. I am shocked, baffled and immensely disappointed to discover that contrary to expectations my team will not be able to conduct code reviews from within their IDE.

In common with many other posters here the IDE integration was an absolutely indispensible feature. As a JIRA / SVN / Eclipse / Mylyn / Java / JavaScript / etc. shop our main motivation for evaluating Atlassian was the proven execellence (?) of the IDE connector (Mylyn + JIRA is amazing). We have already evaluated non-integrated code review tools but they were klunky and time-consuming to use. Reviewers *need* integrated access to the IDE’s integrated code analysis tools in order to make sense of the code under view.

Your IDE integration was your Unique Selling Point. There’s precious little point in my even bothering to invest any more time in evaluating further FE/CR.

By Adrian Price on February 20, 2012 / Reply
Your marketing BS about refocusing effort to create a better overall experience is insulting. You are pulling support because some number cruncher decided that the income generated by the connector did not cover the cost of development. You would be better served by being honest. We will still hate the decision, because we as users do not care about your bottom line, but at least we will respect your corporate honesty.

By Spencer Stejskal on February 23, 2012 / Reply
As we are evaluating Crucible. This was the development team’s first question, “Does this integrate with Eclipse?” I was sure that it would…. I was wrong. Please reconsider this decision. We were so close to buying a license, but now we are continuing to explore other code review tools because of this missing feature.

By Clint on March 15, 2012 / Reply
Remove Eclipse support for Crucible made the life of many of your customers very difficult. I understand that the cost needs to be considered but hopefully Atlassian’s growth can justify that. IDE integration is a big time saver for many users and one of the main reasons to use Crucible.

Please add my vote to having this functionality restored and especially for restoring support for Pre-Commit Reviews for Eclipse.

By Crucible User on April 10, 2012 / Reply
Here’s another requesting for you to restart the work on the connector and add back support for crucible. I’m a long time Eclipse and IntelliJ user and was just recently introduced to crucible. The web interface is nice, but for anything but the most trivial code reviews it comes up short compared to using an IDE.

Since I already had the connector plugin installed (in Intellij, to access JIRA) I was sure it would support crucible reviews. In fact most of your online documentation still describes the connector support as if it still works. You can still add a crucible server using the plugin, although it doesn’t seem to do anything. Imagine my surprise to find out the reason why I couldn’t get it to work is because it’s no longer supported!

So, please add this support back. IDE integration is much more important than having a nice Web UI.

And in the meantime, please update your online documentation to make it clear that this feature is no longer present in the plugin.

For those who are looking for a code review tool with IntelliJ integration, I’ve been told that reVu (https://github.com/syllant/idea-plugin-revu) looks promising.

By Phil Shapiro on May 14, 2012 / Reply
I downloaded this connector soley so I could do code reviews from inside the eclipse IDE, after discovering that this functionality was removed I have uninstalled it again.

Reviewing code in the web browser is clunky, trying to edit code while jumping between reviews in one page and code in the other is downright tedious. Please put at least this function back in please!

By Roger Watkins on July 5, 2012 / Reply
I can’t believe what a stupid decision! I don’t know what statistics you’ve gathered over the years but everyone I know prefers IDE integration over using a web site.
Applications in the web are inherently wrong. The web was not created for applications and those miserable attempts with DOM/JS/Ajax will never make it. You need a total redesign like using applets but nobody will adopt it.
So instead of trying to create the uncreatable, just make a nice integration with the most popular IDEs and you will be rich.

One thing IDE rules is code navigation. How do you image I can do code review without the ability to quickly and easily jump through code? Probably instead of duplicating your Crucible logic in IDE plug-ins, you have chosen to duplicate the IDE logic into a web-based Crucible?!

By Stan on July 10, 2012 / Reply
Fire your PM or VP of Engineering, we need crucible in the IDE.

By Cheko on October 11, 2012 / Reply
Unfortunate that Atlassian can not find resources to keep up basic features in IDE-integration.

It is difficult to review code in browser without code-navigation. It is also troublesome to apply review decisions in code by having a browser side by side with IDE. Is this the view Atlassian has to offer to customers?

By Petri Sirkkala on October 24, 2012 / Reply
This is surely unbelievable. When I did a demo of Crucible to my dev team, the first question they asked was “Does this integrate with Eclipse IDE?”. Can’t believe that Atlassian made the decision to remove IDE integration from a code review tool. It’s not a dump of text we are trying to review, it’s code that flows through various modules and you need to be able to navigate through it to do a proper review.

At best now Crucible sounds like a Code View/Discussion tool, not a proper code review tool. Quite disappointing as now for us Crucible is a no go.

By Chai on November 29, 2012 / Reply
Just saying what has already been said, but very disappointed with this move. Not being able to do a code review in your IDE where all you code lives seems very strange. It really disrupts my workflow having to switch from my IDE to a browser.

By Paul on December 3, 2012 / Reply
The only features I use in the plugin are the Fisheye & Crucible integration. Haven’t updated in ages because I don’t want to lose these features!

By Pauline on December 10, 2012 / Reply
I’m so pleased you ditch the IDE support for Crucible.
Doing code review in my browser is so much comfortable !
That was a very clever move :p

By Guillaume on January 9, 2013 / Reply
Just piloting the use of Crucible. Not integrating with Eclipse will be a showstopper.

The web interface is inadequate for code review, its not good enough to replace the IDE. A better decision would be to get rid of the web interface.

By Mark Rogers on January 9, 2013 / Reply
Is the open-source version at https://bitbucket.org/atlassian/connector-idea keeping up? Does anyone have build instructions? I’m seeing

[ERROR] The project com.atlassian.connector:atlassian-idea-plugin:3.0.10-SNAPSHOT (/Users/thams/connector-idea/atlassian-intellij-connector/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not transfer artifact com.atlassian.connector:atlassian-connector-parent-pom:pom:2.1.4 from/to atlassian-restricted (dav:https://maven.atlassian.com/content/repositories/atlassian-restricted/): No connector available to access repository atlassian-restricted (dav:https://maven.atlassian.com/content/repositories/atlassian-restricted/) of type default using the available factories WagonRepositoryConnectorFactory and ‘parent.relativePath’ points at wrong local POM @ line 4, column 13 -> [Help 2]

By Kurt Thams on February 4, 2013 / Reply
- A better place to ask this question is http://answers.atlassian.com or create a support issue.
  
  By Jens Schumacher on February 4, 2013
- Okay, asked: https://answers.atlassian.com/questions/133100/how-to-build-open-source-version-of-intellij-ide-connector
  
  By Kurt Thams on February 4, 2013
I really don’t understand the rationale behind removing IDE support for Crucible. Crucible is a too for code reviews (i.e. a developer tool) so being able to use it from an IDE is a core requirement. I would love to hear how you came to the conclusion that removing this integration was a good idea.

By Charlie Robertson on February 14, 2013 / Reply