Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-3216

Description for repositories

    XMLWordPrintable

    Details

    • Feedback Policy:
      We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      Atlassian status as of September 2018

      Hi everyone,

      Thanks 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.

      This suggestion is a priority for the Bitbucket development team and is on our roadmap, however we're not able to provide a timeline for when it will be resolved. Learn more about our process here.

      Cheers,
      Anton Genkin

      Product Manager - Bitbucket Server

      Original request description

      On project pages, where all repositories within that project are listed, there is no description column (like there is a description column for each project on the frontpage of Stash).

      With the fixed hierarchy of only two layers (Projects-Repositories) proper categorisation of repositories can become cumbersome, and providing descriptions against the listing of repositories would help significantly.

      README files within each repository does not suffice.

        Attachments

        1. descriptions-3.2.1.png
          158 kB
          Sylvie Davies [bit-booster.com]
        2. stash_prj_doc.png
          123 kB
          Robbin Bonthond

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              michaelsembwever mck
              Votes:
              184 Vote for this issue
              Watchers:
              96 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: