1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #5356 closed

Labels for issues? (BB-6550)

JP Richardson
created an issue

I primarily use Github, but I'm definitely attracted to Bitbucket. One thing that I wish Bitbucket would have that Github has, is labels for issues. Is that something that you've considered or are considering?

The beauty of labels is that they bring simplicity and solve a number of use cases. With labels, you could eliminate the "kind" field and the "priority" field.

Official response

  • Rahul Chhabria staff

    Hi everyone. We’re always working to balance many priorities and are busy at work on highly voted features like code search (#2874), large file support (#11204), and more code review improvements (#589, #7042, #5652, #8995). As a result, we do not plan to implement labels for Bitbucket issues in the near-to-mid future. We know this is a highly voted feature and this will be a disappointment, but ultimately it comes down to prioritization. We’ve recently improved the JIRA/Bitbucket integration process and updated the Bitbucket app switcher (#9436), so if you haven’t given JIRA a try it’s easier to get up and running than ever. Please keep the feedback coming - we appreciate it.

Comments (61)

  1. Alexandru G

    Guys, the only way to tell developers that we need/want this feature implemented is to vote for it from upper right of this page and maybe to start watch this issue. When there are only 2 votes for this feature, I don't think the devs are willing to invest time in something they are not sure that will be used by users.

    Vote, watch and have patience.

  2. Anonymous

    Can you enlighten me, what does labels gives you, that you don't find in components? I agree, that this is something a bit different, but after all, can't we use components instead of labels until labels are implemented? This is always something against nothing, right?

  3. JP Richardson reporter

    @trejder I'm not sure what components are as I don't really use BitBucket anymore. Labels allows a development team to define a workflow. e.g. specifically agile use cases. Here is an example of another use case: https://github.com/rethinkdb/rethinkdb/issues

    As it stands now though, I'm a paying user of Github and am pretty active on the site, so I'm not sure that even labels could get me to consider BitBucket anymore whereas when I posted the issue I wasn't committed to Github yet.

  4. Anonymous

    JP Richardson If I'm getting the "labels" idea quite right, components at BitBucket are pretty much the same, with the one, small but important exception, that you can assign only one component to each issue, whereas you can have multiple labels for one issue.

    I still don't get the connection between labels and agile development. I understand labels pretty much the same like tags in a blog.

    I did a quick reply last time and I haven't noticed that your original issue posting took place nearly a year a go, so I understand, this is a bit off-topic talk right now.

    Which doesn't change the fact, that the original idea remains -- lables would be something just great for BitBucket issues system. But, on the other hand, I understand that this is one of the features in JIRA, and BitBucket's issue system should not duplicate paid flagship of Atlassian, so chances, that they'll ever implement lables to BitBucket are quite small.

  5. JP Richardson reporter

    @trejder The key idea for labels is that you can assign more than one label. You're right, they are exactly like tags. Regarding agile development, let's assume you have a labels named "backlog", "sprintlog", "bug", "enhancement". So issues that are on the backlog that are bugs would be labeled "backlog" and "bug". Much like here: https://github.com/jprichardson/string.js/issues?direction=desc&sort=created&state=open Yes, I know that BitBucket supports assigning an issue a bug, but that's not the point. The point is that labels/tags allow developers to define workflow models and taxonomies that make sense to their team. I find them so valuable that I'm much more willing to pay Github than to use BitBucket's free offering.

  6. Eric Franz

    Labels that work as well as GitHub Labels would make the issue tracker 100% more useful. I can simulate multiple fields by having labels grouped by color and text prefix.

  7. Adam Faszl

    This would be very nice to have. Issue trackers are frequently used for lightweight project management. Tagging supports all current workflows and allows for many productivity tweaks depending on team and project requirements. A few use cases:

    • Hierarchical components: say a project has both physical (i.e. hardware) and software deliverables. The top-level deliverables are the client and corresponding server platforms. An issue with the "server" deliverable could easily be either a hardware or software problem, and boolean tag filtering makes it easy to distinguish between the two, prioritize, and assign the right people.

    • Project requirement considerations: perhaps some features have been designated essential, others as "if time permits." Any issue might be either; without tags we would have to resort to using priorities or milestones as tags and not as intended, leading to potential confusion.

    • Component overlap: it could be helpful if, for instance, a UI bug causing the "Logout" button to not display might be found in both a list of UI component bugs and authentication component bugs.

  8. Luke Watts

    I completely agree, I had a look through Jira and whilst it's a great bit of software it's total overkill for a lone developer looking to tidy up issues across a couple of projects

  9. Damir Vandic

    I'm also in doubt what to do. I was thinking of using Bitbucket + JIRA OnDemand, with this setup you get unlimited private repos and a good issue tracker (and a good integration between them) for $10 p/month. In any case, I hope this feature gets implemented!

  10. Victor Olex

    Any word as to when this might be added? Tagging would allow for organizing issues in any way that makes sense for the project without growing the number of settings on the Create Issue screen. For example I could add a tag, which represents a product driver or a theme or to maintain a short priority list across components.

  11. Alexander Schittler

    While I understand you want to keep some features restricted to JIRA, this is something required for feature parity with Github. If you want the open source crowd to pay more attention and not just the small closed source people to use Bitbucket this would be a thing to do.

  12. Anonymous

    Maybe you might just rename "Component" label to "Labels" everywhere and allow it to contain list of values.

  13. Dumont Cyrille

    Tags should've been available from the start. I'm using Bitbucket as a free tier but will change to the paid one soon.

    BUT

    • JIRA,no thank you (Don't want to jump between sites. Within Bitbucket is perfect).

    • I'll look for an other service within 6 months if nothing is done regarding this(as with saving searches...)

  14. Ken Zangelin

    I completely agree with the comments above. I use github at work and bitbucket for personal use, as I get free private repositories in bitbucket. But, I really miss the labels and milestones for the issues ...

  15. Krzysiek Domański

    There's really no excuse for not having it now, sounds to me like a marketing ploy to get people to buy JIRA integration.

    Well, even if it's true I would not blame Atlassian for such measures. They still deliver a great free product, it's understandable if they would like to make some money somewhere.

  16. James Howe

    Krzysiek Domański I already pay for Bitbucket so I have no grudge in paying for a service that meets my requirements, however I refuse paying for JIRA integration when I all I really need is the ability to add a couple of labels to an issue...

  17. James Howe

    Krzysiek Domański the whole idea of "premium" features doesn't seem to be the Bitbucket motto. It would appear that they don't seem to think it's worth the effort, I would imagine most folk either use simplistic issue tracking where they can get by without labels or more complex issue tracking where JIRA becomes beneficial. It's the folk inbetween (like me) who seem to be missing out sadly :(

  18. Ross Rogers

    FYI, if you are using components as a proxy for labels and you want to sort on the labels, you can append &sort=component to the URL to get it to sort by the component field.

  19. Hai Bison

    Like Ross Rogers said, components work like labels. That's great :-)

    Component names are printed along with issues while viewing the whole list. To me, that's good enough.

  20. Denison Martins

    +1 DiRaven NA Robert Reiz @aldango. JIRA is so much more than labels. A lot of devs (and myself included) I know won't come fully to Bitbucket just because of this lacking feature. The use of labels can be as much complex/flexible as the user wants, and thats the beauty of it. It seems that could be used to attract more devs into the whole BB thing and as a consequence they would eventually stumble upon the JIRA.

  21. Garret Wilson

    The problem is that JIRA is a monster; it is almost impossible to figure out how to configure it without spending a week just to get issue/workflow/permission schemes correct (they are buggy, inconsistent, and half-baked---some use existing default ones but not the ones "named" default, and other create new ones for each project). Plus JIRA users aren't integrated into Bitbucket---you have to create a completely parallel set of users. It's a nightmare to switch to JIRA just to get labels.

  22. Rahul Chhabria staff

    Hi everyone. We’re always working to balance many priorities and are busy at work on highly voted features like code search (#2874), large file support (#11204), and more code review improvements (#589, #7042, #5652, #8995). As a result, we do not plan to implement labels for Bitbucket issues in the near-to-mid future. We know this is a highly voted feature and this will be a disappointment, but ultimately it comes down to prioritization. We’ve recently improved the JIRA/Bitbucket integration process and updated the Bitbucket app switcher (#9436), so if you haven’t given JIRA a try it’s easier to get up and running than ever. Please keep the feedback coming - we appreciate it.

  23. Faraaz

    please add labels it is highly useful and one of the basic requirement to keep track and categorise the issues. It is painful to move to JIRA just for this.

  24. Christopher Fuhrman

    I agree with JIRA being a monster (having labels there isn't going to make me switch). Simplicity is great (even Gmail has labels!). The official response from Rahul Chhabria kinda sounds like "no free labels," which I admit is fair. I'm in education and will likely migrate to using private GitHub repos for issue tracking (that I can get for free, but haven't done so as yet because it requires making requests). BitBucket's sourcetree is useful to learn with (on par with GitHub Desktop), but JIRA is just too heavy for undergraduate classrooms.

  25. Michael Domhardt

    It's the same here. Me and my students switched from BitBucket to our own GitLab instance. The labels in GitLab are used very well in contrast to our JIRA server. JIRA brings too much of an overhead to our software projects.

  26. Mihael Schmidt

    Tags would be great because it is so much more than assigning an issue to a component or a milestone.

    How about tagging an issue as a beginner task. The label "beginner" would be great. Then everybody new to the project but wanting to contribute could pick these issues.

    Bitbucket is limiting my options on how to use a tool. Please make it more open.

    thumbsdown for closing the request.

  27. Log in to comment