Projects feature should be optional for both team and personal accounts

Issue #12400 open
Serguei Mokhov
created an issue

Hi,

The recently added fiasco projects feature is inconsistent:

  • mandatory projects under team accounts
  • no projects allowed for personal accounts' repos

This seems bizarre and at the very least inconsistent.

Many users either have a notion of a project per repo or project per team. Conversely, a project may span across teams and repos. This is includes repos under individual accounts. Why do you force us to have a project for team accounts but not allow for projects under individual accounts?

Therefore, the projects feature is otherwise redundant and should be optional for those wishing to use it, especially you don't have it for individual accounts -- it means it must be possible for team accounts to disable it as well. It should really be an optional feature available to both account types!

Comments (5)

  1. Gary Sackett staff

    Hi Serguei, We appreciate the feedback. Projects are an integral part of how teams work in Bitbucket Server, and was a highly requested feature from users looking for better ways to organise their repositories.

    While a highly requested feature, we also understood it would add overhead for individuals who only maintain a couple of repositories. Therefore we introduced Projects as a Team only feature.

    Our goal for Projects in Bitbucket was to add an additional layer of structure without introducing navigational overhead. From the Dashboard you can still access your repository directly. Recently accessed repositories sit at the top of the list and can be accessed from anywhere via the global navigation bar. If you are a member of multiple teams or have a number of projects, you can now filter the list of repositories by owner and project name.

    Most of these specific items have been requested in: https://bitbucket.org/site/master/issues/12256/allow-repositories-to-be-in-multiple https://bitbucket.org/site/master/issues/12278/project-administration https://bitbucket.org/site/master/issues/12260/project-level-issues-wiki-and-downloads-bb

    We will continue to iterate and improve projects over the next few weeks and hopefully address some of the feedback we've received. We followed up last week with http://blog.bitbucket.org/2016/02/24/new-improvements-for-bitbucket-cloud-projects/.

    We know this has been a big change and change can be frustrating. But we hope you'll take a moment, give your new project a name and avatar, and start organizing your repositories. We think you will like it.

    Cheers, Gary

  2. Serguei Mokhov reporter
    • changed status to open

    Gary,

    Before you mark it as invalid, the core of the request is not addressed:

    • I want to have optionally* projects for personal repos, as it makes sense to have a projects for personal repos or forks of repos from other teams/projects. The fact that you don't have projects for individuals but projects for teams already means they can be optional.

    Projects feature should be defined something per individual to allow groupping any repos the individual involved in in any teams to group into their project they defined, like a personal folder that they could share if wanted. But then again, you have teams for it already.

    Likewise, projects when you fork a repo from team to team, still belong to the same project, but we are forced to create new projects for the forks, when they are in fact still the same project. This makes things cumbersome and inconsistent and the top navigation menu useless when the same , such as Projects, especially when to have tons of repos and teams, like in my case.

    The projects feature should really be optional or be as a tag.

    The fact it was a highly requested feature does not make it to be mandatory for all. I'd be interested to see the stats from those who were polled to have as a desired feature vs. how many issues and votes it created when the feature rolled out.

    You write:

    • "While a highly requested feature, we also understood it would add overhead for individuals who only maintain a couple of repositories. Therefore we introduced Projects as a Team only feature."

    This is why it should be optional! Only for those who need it. Plus, it is inconsistent!

    You write:

    • "Our goal for Projects in Bitbucket was to add an additional layer of structure without introducing navigational overhead."

    From all the issues and comments from the original blog post it seems you clearly failed in achieving that goal. It is now harder to navigate with extra overhead that was needed.

    • "From the Dashboard you can still access your repository directly. Recently accessed repositories sit at the top of the list and can be accessed from anywhere via the global navigation bar. If you are a member of multiple teams or have a number of projects, you can now filter the list of repositories by owner and project name."

    This is not of relevance here since the Dashboard does not list projects for individual repositories. Though thank you for bringing back the last modified column.

    • "We know this has been a big change and change can be frustrating. But we hope you'll take a moment, give your new project a name and avatar, and start organizing your repositories. We think you will like it."

    My organizational attempt at this ends up in structure like

    NAME / NAME / repo
    

    i.e., not helpful. Most project names will be identical to team names NAME, which is kind of redundant.

  3. Log in to comment