Skip to end of metadata
Go to start of metadata

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:

  1. Navigate to your bb101repo.
  2. Click the settings  button.
    The system displays the Repository details page. 
  3. 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.
  4. Click Private wiki.
  5. 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.

  1. Click the Wiki option on the repository menu bar.
    By default Bitbucket displays the wiki Home page.
  2. Click Edit.
  3. Make your changes to the page content.
    You may want to change the Welcome heading 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.
  4. 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.
  5. 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:

  1. Navigate to a repository.
  2. Click the repository settings button.
    The system displays the Repository details page. 
  3. 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.
  4. Click Private tracker.
  5. Press Save.
    The system enables the Issue menu item for your repository. You will see there are now a number of settings available.
  6. Click Components.
    You can use components to group issues within a project into logical groups.
  7. Enter a component, for example, Site Design and press Add.
  8. Add a Performance component as well.
  9. 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.
  10. 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.
  11. 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.

  1. Go to the repository's Issues tab.
  2. Click Create Issue.
  3. 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.

  4. Press Create issue.

Next Steps

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.

13 Comments

  1. Anonymous

    Is there any support for a public wiki in bitbucket? Somewhere that users can report help/tips/tricks?

    1. You can make your Wiki public.  Any user with access can clone and push content changes to it.

  2. Anonymous

    It seems that the wiki currently supports Markdown instead of Creole markup, right?

    1. You can choose which Markup language you want to use in your Wiki.

  3. Anonymous

    Hey, found a quick typo,

    "track your projects feature requests"

    Should be "project's". It's possessive, right?

    1. By George I think you're right! Thank you for your comment.

       

  4. Anonymous

    Hi,

    Is there any support to configure the Status in issue Tracking , We need to add new status like "Close, Tool limitation, Defer...

     

  5. Anonymous

    I have created a wiki page, but I cannot access it, it does not appear referenced anywhere? I can just access the Home page. Can someone help me ?

  6. My company is using JIRA OnDemand, and there is a primary user in Bitbucket that owns all of our repos. I am not the owner of that admin account, but I believe that the DVCS Connector is set up correctly, because:

    a) when I push a commit that contains an issue number in the comment, it shows up in the appropriate place(s) in JIRA

    and

    b) when I am on an issue page in JIRA and I click the link for "create branch", I am linked to the appropriate Bitbucket repository 


    My questions:

    From the Bitbucket repository, there is no visible link to JIRA as the "Issue Tracker" for the repo. Have I simply overlooked something, or is there a configuration setting that needs to be changed?

    From the corresponding JIRA project, there is no link to the Bitbucket repo (aside from the various commit links in specific issues and activity feeds).

    I have the same basic question regarding linking between the Bitbucket repo and the associated page in Confleunce.


    1. Zach,

      In the repository admin page, under the Links section, you (or your repository admin) can find buttons to add links to Jira, Bamboo, Crusible and Jenkins.

      Hope this comment helps

    2. You will have to link your repository (as stated in the other comment) by setting up both the DVCS connector and linking your repository to JIRA.

      You will need the URL for your OnDemand JIRA instance (https://yourname.atlassian.net), and the project key

      1. Log into Bitbucket and navigate to the repository you want to link.
      2. Click Links.
      3. Click JIRA
      4. Add your JIRA URL and Project Key.
      5. Click Save
      6. It may take a few to several min for the links to show up in the commits.

       

  7. Israel and Dan – thank you, but I don't think you understood my question. The "links" section is already successfully configured – when I push commits to my repository, the links to the JIRA project are made into clickable links as expected. What I am NOT seeing is a link in the repository header that points to JIRA as the issue tracker for that particular repository. 

    You may ask why I care about this. If I am looking at a commit message in BitBucket and it has tags in it that link to specific issue(s) in JIRA, and I can get from JIRA to the relevant commits, merges, and branches in BitBucket, then why does a missing header matter? 

    use case:  Joe is a developer and begins work on this project by cloning the repo. He discovers a bug and wants to make sure that the lead developer is aware of it. He goes to the overview page in BitBucket, but does not see an "issue tracker" link in the header where one would appear if the project were using BitBucket's internal issue tracker. Since he is new to this project, he has not viewed detailed commit messages from other developers that link back to specific issues in JIRA. He concludes that this project does not have an associated issue tracker so decides to abandon his interest in the project.

    1. Good day Zach,

      You are correct I did not understand your question. I agree with your premise and would strongly encourage you to open a feature request I couldn't find an existing issue which matched your question, so I have narrowed the field of issues in the lnik I provided to an issue+link search.You could pretty much copy and paste your post here into the issue description. For a title I'd suggest something like: Link JIRA issues from Bitbucket navigation.

      Thank you for taking the time to write this up!