Details

    • Type: Suggestion
    • Status: Open (View Workflow)
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Repositories
    • Labels:
      None

      Description

      Atlassian status as of December 2016

      Hi everyone,

      Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Server.

      We spend a significant amount of time on an ongoing basis to determine our product investments in Bitbucket Server. Unfortunately, we are not currently planning to address this suggestion in the next 12 months. In the last 12 months, we've resolved 10 of the top 30 feature requests, and our upcoming roadmap includes a number of other top voted suggestions, including in-browser editing, improvements to search functionality, better JIRA integration, and providing an even better code review experience.

      In the meantime, we hope that everyone might consider an established 3rd-party add-on - Categories for Bitbucket. Our ecosystem is an important aspect of the product, providing flexibility where people want different or additional functionality, and maintaining simplicity where they don't.

      I understand that this may be disappointing, but we believe it’s important for us to be open, honest and transparent with our customers. Product feedback is collected from a number of different sources and is evaluated when planning the product roadmap. You can learn more about our process here.

      Norman Ma

      Product Manager - Bitbucket Server

      With the fixed hierarchy of only two layers (Projects-Repositories) proper categorisation of repositories can become cumbersome.

      This can greatly alleviate this in large organisations with many repositories.
      Tags or Labels here are the same concept as "Labels" in Jira. This is not tags as in `git tag…`

      In our use case, some things tags would be used for is specifying:

      • development teams involved and/or responsible for a repository,
      • primary technologies involved,
      • primary systems components involved,
      • status flags, etc

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                michaelsembwever mck
              • Votes:
                66 Vote for this issue
                Watchers:
                31 Start watching this issue

                Dates

                • Created:
                  Updated: