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.

Read up on how to write brokers.

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:

• Akismet, you can protect your issue tracker from spam.
• Tab-width, you can now choose between 2, 4 or 8 spaces.
• Notification system got a massive overhaul.

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:

• A link to the user’s profile
• A submenu that lists the user’s public repositories
• A link to send a message to the user, using the Bitbucket messaging system

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:

• On paginated pages, press left/right-arrow.
• On all pages using the full-size avatars, like the news-page, hover an avatar and wait.. The avatar dropdown also gives a shortcut to a feature we’re currently working on, that’s already in a working state.

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)