When you add a repository to Bitbucket, you can also enable a wiki and an issue tracker for that repository. The wiki is a simple place to keep documents. The issue tracker is the place to track your project's feature requests, bug reports and other project management tasks. The wiki and issue tracker do not depend on each other. You can choose to set up each one separately. This page leads you through the basics of using the wiki and issue tracker.
Step 1. Configure your wiki
To enable the wiki for your repository, log into Bitbucket and do the following:
- Navigate to your
- Click the settings button.
The system displays the Repository details page.
- Choose Wiki settings from the left-hand panel.
The system opens the Wiki page. A private wiki is only visible to people who have permission to see it. A public wiki anyone can view, edit, or create pages.
- Click Private wiki.
- Press Save.
The system enables the Wiki tab for your repository.
Step 2. Update wiki pages
A Bitbucket wiki is a repository like any other, you can clone it and push changes to it. To create content, the wiki uses Creole markup.
- Click the Wiki option on the repository menu bar.
By default Bitbucket displays the wiki Home page.
- Click Edit.
- Make your changes to the page content.
You may want to change the
Welcomeheading to say
Welcome to the bb101repo.
If you want to do something more elaborate but you aren't sure how, take the Wiki markup link to view the help. The Bitbucket wiki uses the Creole syntax.
- Enter a comment in the Message text box.
This is a commit message. What you enter here will appear in the page history above the relevant commit entry.
- Click Save.
The system displays your home page with the new heading.
Step 3. Configure your issue tracker
To enable the issue tracker for your
bb101repo, log into Bitbucket and do the following:
- Navigate to a repository.
- Click the repository settings
The system displays the Repository details page. icon.
- Click Issue tracker settings.
The system opens the issue tracker page. A private issue tracker is visible only to people who have permission to see it. A public tracker anyone can view or create issues.
- Click Private tracker.
- Press Save.
The system enables the Issue menu item for your repository. You will see there are now a number of settings available.
- Click Components.
You can use components to group issues within a project into logical groups.
- Enter a component, for example, S
ite Designand press Add.
- Add a P
erformancecomponent as well.
- Ignore the Milestones setting.
A milestone is a subset of a version. It is a point that a development team works towards. Like all settings Milestones is optional. You won't need it for this tutorial so leave it unset.
- Click Versions and configure the setting by adding a 1.0 value.
A version helps you schedule and organize your releases and track the release that is affected by a bug.
Click Mailing list and configure the setting by adding a back up email for yourself.
These are email addresses that receive notification when a user creates an issue.
Step 4. Create an issue
Creating bug reports, improvement requests and tasks is as simple as creating an issue of the appropriate type.
- Go to the repository's Issues tab.
- Click Create Issue.
- Fill in the fields on the issue form.
The system displays the create issue panel:
Notice that this issue tracker is not using a milestone value.
- Press Create issue.
Next Steps: Set up SSH for Git or Set up SSH for Mercurial
Up until this point, you've used HTTPS to access your Bitbucket repos. HTTPS access requires that you give a username and password for each operation. If you are doing a lot of work, this can get annoying. In the next section, you learn how to use secure shell (SSH) to access your Bitbucket repos.