How is binary files to "Snippets" different than a dropbox / s3 / slack link? I guess that there is some convenience factor (1 product), but given that binaries and snippets are not version controlled seems out of place.
Actually, they are versioned. Each snippet is backed by a git repo (or hg, you can choose at creation time). You can clone it to work on it locally too, and push back just like a regular repo. More info here: https://confluence.atlassian.com/bitbucket/snippets-71909508...
Here's the 7th. Every Bitbucket Server admin has a double-digit long list of watched issues. And to go on, plenty dive into Atlassian, because of the ecosystem, but the ecosystem is not at all symbiotic i.e. the products are built separately, implement same functionality, same UI concepts in totally different ways.
I know the link is not about the onpremise version but given the onpremise solutions' quality, bitbucket.org is well.. In the same bucket.
I desperately wanted to use Atlassian products across the entire workflow at my last job, but it's just too much. Like you said, separately-built products implementing identical functionality, sort-of-similar-but-still-different UIs, it's maddening.
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!
Hi, I tried to get that automated workflow process with pull requests going between my team's bitbucket and jira last year, but it didn't seem possible without other tools.
Can you point me at any documentation that can help me get that set up? Thanks!
I've maintained almost the full Atlassian suite for about 2 years. Yes, they are hard to install and maintain, each product is different, but once you have things set up and working, it's solid.
But, in general, Atlassian software is pretty solid. I doubt you can assume that the stability of Bitbucket is subpar, because their software, in general, is hard to install and upgrade. In fact, I think the pressure from their web properties will make their growing cloud services much easier to maintain.
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.
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.
Ben (Bitbucket PM) has posted an update on the dashboard issue:
> We're working on an update that will allow you to sort by last modified and generally make the dashboard more flexible. I'll post updates here as I have them.
I can't comment on specific timelines, but it's definitely under way!
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.)
Depending on your screen rez, the sidebar may be collapsed by default. Hit `[` (or click the `>>`) to pop it out to see descriptions alongside the icons.
I find the paradigm of "active" vs "merged" branches frustrating and obtuse as it has absolutely nothing to do with git. It just makes it confusing to find a feature branch I pushed without changes intending to work on it later. If that branch is based on a recently merged "development" for deploy my feature branch disappears. In fact, after a deploy development disappears. If I don't want to see a branch I will delete it.
I almost couldn't go on reading when I saw that. Definitely had to cringe. Look, this company makes reasonably decent tools for the enterprise but I seriously don't get how they justify what they call UI design.
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.
1. Configuring build plan branches is a pain, and the way that builds are associated with branches is not obvious.
2. It always takes a few clicks to get where I need to go.
3. We use the Artifactory release plugin. To get to it, we have to go to a build, click on a TINY (5x10 pixels or so) light gray arrow on the far left of the window, click on the build result there, and then the tab for the Artifactory plugin will be visible. This could be partially on the Artifactory folks, but it looks like there was only so much they could do with the API provided to them.
Those are the things off the top of my head. OTOH, it is functioning fairly well for us, once we've learned the quirks. We're in the process of scaling it out to the rest of our 25-developer team—we'll see how that goes...
What would truly be nice would be Hg support in their on site solution. Where is it at guys? We need Active Directory integration if we want to increase adoption of version control in our company.
The general update in the issue description is the one I was referring to. The PMs do regularly review the open issues (and the roadmap) so please do add your comments/votes there! We're not anti-Hg, we just don't have a strong enough case to prioritize it in our Server offering just yet.
45 comments
[ 2.1 ms ] story [ 82.3 ms ] threadI know the link is not about the onpremise version but given the onpremise solutions' quality, bitbucket.org is well.. In the same bucket.
[1]: https://design.atlassian.com/
Can you point me at any documentation that can help me get that set up? Thanks!
https://confluence.atlassian.com/jiracloud/getting-started-w...
Feel free to drop me a line if you run into strife, my email is in my HN profile info.
Please add votes for these issues:
https://bitbucket.org/site/master/issues/12250/project-icon-...
https://bitbucket.org/site/master/issues/12257/sort-dashboar...
takes 4-5 clicks to go to source code view of a branch (1 click in github)
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
and this - https://bitbucket.org/site/master/issues/4779/ability-to-dif...
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.
> We're working on an update that will allow you to sort by last modified and generally make the dashboard more flexible. I'll post updates here as I have them.
I can't comment on specific timelines, but it's definitely under way!
Edit: the answer is to use JIRA, since they are reasonably well integrated in the on-prem solutions. For their site, no idea.
I find the UX/interface of Bitbucket difficult.
Did anyone let the Jira team know? I love Jira, but the UI can be horribly clunky at times.
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...
1. Configuring build plan branches is a pain, and the way that builds are associated with branches is not obvious. 2. It always takes a few clicks to get where I need to go. 3. We use the Artifactory release plugin. To get to it, we have to go to a build, click on a TINY (5x10 pixels or so) light gray arrow on the far left of the window, click on the build result there, and then the tab for the Artifactory plugin will be visible. This could be partially on the Artifactory folks, but it looks like there was only so much they could do with the API provided to them.
Those are the things off the top of my head. OTOH, it is functioning fairly well for us, once we've learned the quirks. We're in the process of scaling it out to the rest of our 25-developer team—we'll see how that goes...
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...
http://movingfulcrum.com/sourcetree-atlassians-most-epic-eng...