Skip to end of metadata
Go to start of metadata

When you add a repository to Bitbucket, you also get an issue tracker. This is the place to track your project's feature requests, bug reports and other project management tasks. We keep the Bitbucket issue tracker very simple and yet somewhat flexible. It has just a few configurable fields (component, version and milestone) – you can use them any way you want.

Overview of the Issue Tracker

The callouts in the image below describe the various areas available on an issue and their purpose. You can watch an issue to receive notifications about changes to the issue.  

Detailed Issue Tracker How To Guides

Wanting Even More Features?

If you find the Bitbucket issue tracker lacks the features you need, you can choose to use JIRA together with the JIRA DVCS Connector or you can use another issue tracker available through Bitbucket services.

43 Comments

  1. Anonymous

    What about a way to integrate our own scripts to submit issues programatically? Is this already possible and I'm overlooking it?

    1. Anonymous

      That would be helpful...

  2. Anonymous

    Like the system but issue tracking needs a small tweak so that items needing to be tested can be identified.  Can accomplish this by either adding a "Closed" status to reflect completion or "Testing" and leave the current "resolved" to reflect completed tasks.  The "Testing" option would have the least impact on existing tickets the system.

  3. Anonymous

    I would be very glad with an estimation field (smile)

    1. Anonymous

    2. Anonymous

      It would be great! Also with spend hours field.

  4. Anonymous

    Almost every aspect of changes to an issue is recorded in the "Comments and changes" section below the issue itself, but for the issue description aka "content", it just says "Content changed". No option to see old content vs new content, or revert back. I would like know what has changed, and in case of abuse/misunderstanding revert back.

    Am I missing a link, or is this thing just missing ?

  5. Anonymous

    I do also think that it's missing the "closed" state!!!

     

  6. Anonymous

    How does one assign a default assignee to the issue tracker?

    This issue reckons it was added in 2008. Has it been removed since? https://bitbucket.org/site/master/issue/176/default-assignee-for-new-issues

  7. Anonymous

    I'd love to be able to assign an issue to more than one person. Currently it's not possible (sad)

    1. Hi, this is a good enhancement request to make. Please go ahead and file one with a description of what you need and why here.  Then, others can vote on your issue!

      1. The way I've worked around this, is to create a team account that all your developers belong to and create all your repositories with the team as the owner. Then you can assign issues to the team instead of just individuals. The problem with this is that the issues only show up in each repository - they don't show up for each team member. To work around this, make sure all the team members are following the team and then they will at least be emailed when the issues are reported or fixed etc. Not sure if this is the best way to deal with this, but this is what I have been doing. I would like to hear what others are doing to work around this.

        1. It seems to me that assigning to the whole dev team is equivalent to leaving a story unassigned. So just leave it unassigned! Assign to a person (or pair) when it's clear who'll be doing it.

  8. Anonymous

    I would like to be able to have a tracking system that is independent of the project. For example, my projects are related to each other, but they are separate (db project and java project). I will end up with 2 issue tracking systems, one for eahc projects. This is ok, but not good. I would like 1 issue tracking system, with a project selection option. This way, I could see everything that is related to the overall project, and also reference tickets of cross-project issue.

    1. This is an interesting enhancement request.  The best place to make these is on our issue tracker.  

  9. Anonymous

    Interesting seems to be a polite way of saying "future project, but not now" (smile)

    1. Ah, I'm the writer, I don't say no or yes to folks development ideas.  The cool thing about the issue tracker is other folks can easily vote for enhancements on the issue tracker.   Also, well the folks that choose ideas are on there too.  

      Your request actually got me thinking about ways we could advertise enhancement requests better — and get other users to vote for them.  Right now, the doc comments get a lot but the comments just don't get a lot of visibility with the development team.  On the other hand, lots of users end up in the docs first with requests — and other users are likely to end in the docs too.  So, it would be a good place to vote. I'm mulling over ways to do it without end up with huge lists of comments with enhancement requests.

      1. Anonymous

        To be honest, I do not think you should open doc comments at all but I think it is wrong not to have them! If you go though the doc comments, most of them are enhancements/requests for things. However, it is natural to have comments after you read something. Therefore, you should not change the natural behaviour of humans (i.e., commenting after reading a document), and instead, build on it.

        Therefore, if you somehow integrate the doc comments into the issue tracker for development. i.e., when a comment is made, it automatically is created as an issue at the issue tracker, this way, the dev comunity will be able to see it!

  10. Anonymous

    I want to hide the code/repo from my testers.

    Is this possible?

    1. You don't say whether the repository is public or private.  If your repository is private, you can control who can view the repository.  

      1. Anonymous

        My repo is private and I want to invite my testers to use the issue tracker and keep the repo private from them as well.

        1. You can make the issue tracker public and leave your repo private.  Then, testers can add issues but not see your code.

  11. Anonymous

    How can I configure bit bucket issue tracker with Netbeans 7

    1. Anonymous

      There is a Netbeans plugin to support Bitbucket It is called BeanBucket. But, unfortunately, it wasn't updated for past year and it's creator claims, that it isn't even in alpha stage, so this plugin is unfortunately completely unusable and project does look like dead one.

  12. Anonymous

    Can you import issues from github into gitbucket issues?

    1. Not at the moment, but we'd welcome this or any other feature requests to https://bitbucket.org/site/master/issues/new.

  13. Is there a way to get exception notifications into bitbucket issues from rails apps?

    1. You could always issues Resource#POSTanewissue from your app. However, just like email notifications on exceptions you may live to regret it. (smile)

  14. Anonymous

    I am currently working on project, and I want ask, can Issue Tracker be use as project management?

     

    1. Hi,

      The tracker was not designed to do project management.  So, on that basis, the answer is no. That said, the Issue Tracker is very customizable in terms of what users can define as components, milestones, and versions.  So, you might be able to define these values in a way you find useful for managing a project.

      Mary 

  15. Anonymous

    It would be so helpful to be able to mark issues as ready for testing before they get marked resolved.  Right now there is no status to mark an issue as ready for testing.  A few others have suggested this too.

  16. Please integrate bitbucket with JIRA!!!

  17. Anonymous

    I can not see a way to delete / close issues. Is there not?

    1. The More button, I agree it is not immediately obvious:

  18. Anonymous

    I like the issue tracker its more than enough for my needs and i will definitely upgrade to JIRA if needed in future - one thing - is it possible to have issue-tracker work like this comments feature that we're using now.

    Id like a forum/Q&A setup at the moment its nearly doing everything i want but id like it to not keep tracking minor changes to the issue like correcting spelling mistakes in the text of the comment. Better still hide those kind of minor typo updates from view since there not a constructive in the tracking of an issue, a typo is just a typo!! This way its like a Q & A forum.

     

    By the way; an unrelated gripe: the CAPTCHA on this page never accepts the first (or sometimes second) CORRECT entry - it always takes 2-3 goes to get past it!! - i use both Linux and Windows, Chrome, Firefox (and unfortunately IE when i have to) and its the same in all environments.

    1. Thanks for the comments. Regarding refining the tracker to not notify on typo corrections, that is an enhancement request you should make on our issue tracker.  As for CAPTCHA issue we are tracking a related problem and it appears yours is related. I don't yet have an estimated fix date. 

  19. It would be nice to see tighter integration with JIRA, like showing open issues from JIRA on the Issues section of the repo. 

  20. I would like to integrate bitbucket with our JIRA server.  I see a statement above about connecting to JIRA but I don't see any instructions on what the integration does or details on setting it up.

    1. Hi Howard,

      I think this is the page that you want: Use the JIRA DVCS Connector Plugin

      Kind regards,
      Andrew

  21. Anonymous

    would be great to be able to define an order of priority for bugs inside the generic priorities. for example, inside blockers i would see:

    ****

    #1 bug number 1

    blocker

    priority 1

    ****

    #2 bug number 2

    blocker

    priority 2

    ****

    etc

  22. Is there a way to get the "Issues" link on the summary page for a Bitbucket repo to point to a JIRA project? I have the JIRA DVCS connector working, and commit messages are getting linked, but someone just browsing the Bitbucket repo can not easily find their way to the associated JIRA project.