Go to your repository’s admin-tab, and click “Appearance Settings” under “Additional options/settings”.
Here you can choose from a list of themes, and when switching theme in the dropdown the preview to the right will update immediately.
If you like dark themes, check out “Native”.
In your Bitbucket wiki-pages, you have access to data from the issue tracker through a set of wiki macros:
Link to a specific issue
Syntax: <<issue 1>>
Result: A link to the issue with id 1 in your repository’s issue tracker.
Link to an issue query
Syntax: <<query ?status=open&status=new All open issues>>
Result: A link to all issues with status open or new, where the link text is “All open issues”.
List all issues for a milestone (or show count)
Syntax: <<milestone Beta 1>>
Result: A list of issues for milestone “Beta 1”, with links and status for each issue.
List all issues for a query
Syntax: <<issues ?status=open&status=new count|list|compact>>
Result: Lists all issues that match the query (status is open or new) in one of two optional styles, or shows the number of issues that match the query.
<<issues ?status=open&status=new list>> shows a full list of open or new issues, in the same layout as the milestone-macro.
<<issues ?status=open&status=new compact>> shows a list of open or new issues, but only the issue id with a link to each issue in the tracker.
Usage example for count: “There are currently <<issues ?status=open count>> open issues for our project.”
Link to a changeset
Syntax: <<changeset 45cc878df717>>
Result: A link to changeset 45cc878df717’s diff-view.
Written by Jason Kirtland. Thanks!
You want to integrate with your favorite 3rd party service as well? It’s dead-easy.
Maciek Szczesniak wrote a Basecamp broker, and a huge thanks to him! We wrote a Lighthouse broker.
They’re both live, enjoy.
As of now, I’ve just deployed:
Just a quick note that service integration is hereby live.
To go with it, there’s two new help pages: Service Integration & Writing Brokers
Enjoy!
A feature that we haven’t really announced yet, that gives you some handy shortcuts related to a user, is the avatar dropdown.
Anywhere you see a full-size user avatar, such as in the newsfeed, you can hover the avatar, wait a second, and then click the arrow that appears to reveal the user’s dropdown.
As the screenshot above shows, the dropdown contains:
If you’re on a paginated page, like the repository list, you can use the left and right arrow keys to navigate to the previous and next page.
A while back, when we had implemented milestones in the issue-tracker and the wiki was getting more and more useful, we started doing milestone-based development, and recently completed the first one “Above the Law”. Bonus points to the first person to see what we’re basing our milestone-names on…
The major new feature implemented for this milestone is services integration, but it’s still not documented and needs some polishing. Jesper will write a separate post and documentation later on. If you feel brave and wanna take it for a spin, go to http://bitbucket.org/your-username/your-repo/admin/services/ Feedback is much appreciated.
In addition, we’ve made a few tweaks here and there and added some minor stuff that we think can be useful for you. We have started a “Tips & Tricks”-series on this blog that will give some more info and detail on these things, but here are a couple of things for you to try:
The following issues were fixed, list generated using a wiki macro: <<milestone 1. Above the Law>>
#229 Milestone list on query list not sorted (resolved)
#200 Allow RSS for your newsfeed (resolved)
#105 hg convert not always preinstalled (resolved)
#237 Forking private repo should yield private repo (resolved)
#207 Add a slug description of the issue to the end of the URL (resolved)
#147 When hovering a user’s avatar, show a flickr-style menu (resolved)
#173 Multiple SSH keys should have better interface (resolved)
#209 more official way of specifying dupes (resolved)
#199 Allow project admins to specify CSS to use for code highlight (resolved)
#125 wiki changesets and enabling/disabling wiki or issue tracker (resolved)
#228 Column content shouldn’t wrap (resolved)
#223 Title field too short (resolved)
#190 Upon fork, do not create “created” event, rather “forked” (resolved)
#149 Alphabetize repositories (resolved)
#167 Content box on report issue page (resolved)
#67 Forking doesn’t get the proper permissions (resolved)
#281 Give avatar upload details (resolved)
#236 Fork notification on own repo should stay quiet (resolved)
#219 Remove “Enter your message here” from the box when editing wiki pages (resolved)
#206 add bump button for issues (resolved)
#239 Issue notification e-mail reveals addresses of other followers (resolved)
#241 Newsfeed needs paginator at the bottom too (resolved)
#247 improve layout of permissions section on Admin page (resolved)
#254 Hook when pushing displays size per repo, not size in total (resolved)
#235 Repository dropdown on top should segment things (resolved)
#217 Sort repositories dropdown (resolved)
#222 Create wiki macros (resolved)
#261 Serve raw files as attachments (resolved)
#259 user homepage should indicate privacy of repos (resolved)
#176 Default “assignee” for new issues (resolved)
#264 Use sans-serif font in repo displays (resolved)
#263 Disable the “private” checkbox for existing repositories, if limit is reached (resolved)
We recently added padlock icons to show the privacy status for your repos.
The blue “locked” padlock indicates a private repository, either your own or someone else’s repository that you have read or write access to.
The grey “unlocked” padlock indicates a public repository, open for all to see.
Now that our new issue tracker has been live for a while, we would like to ask for your feedback, as well as give you a couple of hints about new features you may or may not have noticed.
Sorting
You can now sort your lists of issues on any of the active fields. Just click the header of the field you want to sort by, and an arrow will show up to indicate the sorting direction. Another click will reverse sort on the same field.
Advanced query
This is a powerful tool for narrowing down your list of issues. You can even make handy bookmarks in your browser for e.g. “Incoming issues”, “Open issues assigned to me”, or something more complex like “Issues targeted for version ‘2.0’, milestone ‘Beta 1’, where summary contains ‘[foobar]’”.
Here’s how: In the issue tracker, click the “Query” button to bring up a page that asks you to add filters using the dropdown to the right. To create a query that returns “Open issues assigned to me”, you could add the following filters:
Clicking “Update query” provides you with a list of all new and open issues assigned to you. If you look at the URL for the resulting page, you can see that “?status=open&status=new&responsible=eirik” is appended at the end. This means that if you bookmark the results page in your browser, you can use that bookmark to quickly access “Open issues assigned to me” later on.
Remembering your query
After performing an advanced query, notice that a new button shows up:
Clicking the “Edit query” button brings you back to the advanced query page, with the filters from your previous query already set. From here, you can either click the “Remove” icon to the right of each filter to remove them, edit the content of each filter, or add new ones to update your query.
Also, after performing a query, and then clicking an issue in the results page, you will find a “Back to results” link, that brings you back to the list of results from your previous query.
Drilling down
Did you notice that you can click any value for e.g. Responsible or Type in the issues list? This is a really quick and efficient way to narrow down the list to only the bugs you’re interested in seeing. For instance, I often start with the full list of issues, click on my username in the Responsible-column, and then I see all issues assigned to me.
Another usecase for this is if you want to triage incoming issues, you can just open the full list of issues, click “New” in the State-column, and you’re left with a list of all un-handled - “New” - issues.
As with advanced queries, we save the choices you’ve made while drilling down the list of issues, so if you click an issue in the list to make changes to it, you can always click “Back to results” to go back to your drilled down list of issues. Clicking “Edit query” after drilling down a bit too far even lets you remove an un-wanted filter.
Milestone/Component/Version
We added three new fields to the tracker for this release. From the admin page for your repository, click “Issue Tracker Settings”. This brings you to a page where you can modify the contents of each field.
These fields give you the possibility to tune the tracker to your specific needs, and give large projects better granularity for issue tracking and handling.
Feedback: We prefer to get feedback on the tracker either through our Google Group, or you can log enhancement requests and issues in our own tracker: http://www.bitbucket.org/jespern/bitbucket/issues/
Thanks :)
Here at Avantlumiere, we just love it when our users are creative on our behalf. Be it suggesting cool features or writing tools that work with Bitbucket, it’s a great feeling.
This time, Peter Hosey has been creative and created a Mercurial extension that allows for a different style of specifying URLs to Bitbucket.
$ hg clone bb://username/repo
..or..
$ hg push bb://username/repo
..or how about..
$ hg push bb+ssh://username/repo
How cool is that? For those of you who have used bzr, and like the lp: style syntax, this comes close. Here’s how to install it:
$ mkdir ~/.hgext
$ hg clone https://bitbucket.org/boredzo/bitbucketextension/ ~/.hgext/bbext
Now make your ~/.hgrc look like this:
[extensions]
bitbucketextension = /my/home/dir/.hgext/bbext/bitbucketrepo
That should do it! Thanks Peter!
There’s a new Django mirror up, this time just the trunk. It’s in sync with the Django SVN, but this time it’s only 21.7 mb, and not the full 137.5 mb.
Go fork, play with it, let loose!
Our server center in Amsterdam, was down yesterday, receiving a large dDOS. The main server was unreachable in certain parts of the world, unfortunately.
We apologize for the inconvenience. The total downtime was about 20 minutes.
Armin Ronacher of Pocoo wrote a few words about us, and he also decided to contribute to the project with a brand spankin’ new diff viewer! It’s already deployed, so you can all enjoy it now.
http://twitter.com/jespern/statuses/912846854.
Coming soon.
According to Alexa, we’re Big in Japan. Cool!
Eirik has written up a guide on how to use the new issue tracker, and the guide will be posted shortly.
The new issue tracker we’ve been working on lately, is as of now, live! Please check out the previous post for more info on the specifics.
It’s really a big step up, we think, and on a big repository it really shows, too.
Go play with it!
NB: Jesper will be on vacation for one week starting Saturday, August 9th, so no development will be done then, and replies to emails might be a bit slow.
The past few days, we’ve been gathering feedback on the issue tracker, we’ve had a couple of big players interested in moving over their hosting, and this has led us to the decision that the issue tracker needs a bit of improvement.
We’ve brainstormed, and we think we’ve come up with some ideas that take the best from existing trackers, like Trac and Lighthouse, and combines it into a simple flow.
What to expect from the new tracker:
We think that with this new functionality, the issue tracker will be suited for even the biggest development projects!
So we finally got a blog set up. It’s powered by cx, which is a simple Django blogging platform.
We’ll keep you posted on new features and what-not here.