rbbitbucket

4 ms·

1.
by rbbitbucket 9y ago
There's always a reason ;) Being a self-hosted product we have to make tradeoffs for the thousands of people operating (scaling, upgrading, configuring, troubleshooting...) instances. In short, we try to keep the system architecture fa
2.
by rbbitbucket 9y ago
Bitbucket PM here. Thanks for the feedback! Support for punctuation in search is something we knew wasn't ideal when we first added code search. As with all software, there were some technical constraints that made it hard to do. We pl
3.
by rbbitbucket 9y ago
Bitbucket Server PM here. I wanted to address some of these points as there's good news on many of them... Regarding PR comments and line comments, file level comments have also been available from the beginning. There's a comment
4.
by rbbitbucket 10y ago
Read the 2nd link ;)
5.
by rbbitbucket 10y ago
I think you've hit on a really important point. In isolation, a particular suggestion might be something of a papercut with a workaround. An unwanted pull request, for example, isn't going to stop others from getting their work do
6.
by rbbitbucket 10y ago
We appreciate the frank feedback, but I have to disagree with the interpretation. I really hate that we can't say yes to every feature suggestion, and what we _are_ able to talk about seems to come across as non-committal to some. The
7.
by rbbitbucket 10y ago
Bitbucket product manager here. Sorry to hear you've been having trouble. What you describe is most definitely unusual so I'd suggest contacting us (or having your admin contact us) at support.atlassian.com so we can look into it.
8.
by rbbitbucket 10y ago
I'm a product manager on the Bitbucket team. For the first issue you mention, it sounds like you might be using an older version as this has been improved in a couple of respects in the last few releases. Specifically, the create pull
9.
Bitbucket Server 4.10 comes with a new personal dashboard(blogs.atlassian.com)
4 points by rbbitbucket 10y ago|1 comments