Bitbucket secrets (opens in new tab)

I sure hope the Sourcetree team is listening, too. The new UI design in Sourcetree Windows 1.8 is absurd. Currently 50 comments in https://jira.atlassian.com/browse/SRCTREEWIN-4306, all negative, and at least 15 duplicate issues. Mind-boggling that the design team would think that this was a good idea, particularly after MS got hammered for removing all the color from Visual Studio.

And since I immediately reverted back to 1.6, I didn't even realize that people were seeing other issues with performance, or that the new account management was a pain.

I just went to one of my repos on Bitbucket, and it only took me one click to get to the source for master and then another click to get to the source for another branch.

You can also set up a project so the source is shown by default on the "landing page" instead of the overview.

Edit: slight re-wording

If you're logged in, there's a "Vote for this issue" link next to the number of votes in the info box at the top of the issue. (The UI will strongly discourage "+1" comments unless they have something else to say.)

Welp, good luck to them in beating GitHub, haha.

Edit: the answer is to use JIRA, since they are reasonably well integrated in the on-prem solutions. For their site, no idea.

We do have a good sized "fusion" team focusing on product integration these days. Their mandate is to not only smooth out the integration process, but also to build some pretty kick-ass features on top of it. For example, between Bitbucket and JIRA these days you can not only view the code changes that relate to issues (and vice versa), but you can also transition issues through your workflow automatically based on the state of your commits, branches, & pull requests. We're also working on unifying the experience across the products. This started with the Atlassian Design Guidelines[1], but is continuing with product improvements like making the concept of a "project" consistent across Bitbucket Cloud, Bitbucket Server & JIRA (and making it easier to map them together). Integration and distributed systems are traditionally a tough problem in software, but we have some of our best engineers on it, so you can expect the cross-product experience to keep getting better!

[1]: https://design.atlassian.com/

Doesn't "hard to maintain" contradict the "once you have it set up and running"?

Oh shit. I'm just about to deploy a Bamboo instance for the first time. Can you elaborate at all please?

The design principles are an ideal that we're striving for, and while we're proud of the improvements that we've made over the last few years (seriously, look at JIRA 7 vs JIRA 4, 5, or 6) we're always looking for ways that we can do better. JIRA as a product pre-dates not only our design principles but also our first hire of a designer by a few years :) It's one of the most flexible tools in the industry and that (currently) comes with some attached complexity tax. We're continually making improvements to highlight happy paths, simplify onboarding, and even remove some obsolete or under-utilized features, to pare back that complexity. However it takes time and many iterations to get that right. Particularly, when you have to balance simplicity with the "power features" and flexibilty that many customers count on us for. If you have feedback on rough edges or clunkiness that affect you I'd love to hear it! My contact info is on my profile.

If you'd like to read a bit more about Design @ Atlassian, our team posts pretty regularly over at on Medium. This one's a good read if you have a design bent: https://medium.com/designing-atlassian/product-to-platform-e...

Thanks for the answer.

Did they? According to the history that doesn't seem to be the case.

Unless you mean the general post from Sept of last year?

Really sad though, the largest Hg hosting provider _can't_ provide Hg hosting locally. But they can do git...