The current state of group issue boards does not show the "Add issues"
button on the UI for users that are reporters of group child projects.

Alessio Caiazza authored 5 years ago and Mayra Cabrera committed 5 years ago

Root namespaces have storage statistics.
This commit allows namespace owners to get those stats via GraphQL
queries like the following one

{
  namespace(fullPath: "a_namespace_path") {
    rootStorageStatistics {
      storageSize
      repositorySize
      lfsObjectsSize
      buildArtifactsSize
      packagesSize
      wikiSize
    }
  }
}

- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level

Steve Abrams authored 5 years ago and Mayra Cabrera committed 5 years ago

API endpoints for requesting container repositories
and container repositories with their tag information
are enabled for users that want to specify the group
containing the repository rather than the specific project.

These are not required because MySQL is not
supported anymore

All specs passing

The current approach requires catching exceptions to handle these errors
and callers are already handling model validations so it seems more
appropriate.  Also it seemed to convoluted to add this logic directly to
the model since the model needs to check too many possible associations
to determine whether or not there are more than one cluster since the
model doesn't know what it's being created on. Additionally we only
wanted to validate during create to avoid the risk of existing models
becoming invalid by many different edge cases.

All specs passing

All specs passing

All specs passing

All specs passing

Adds two methods for us to extend in EE:
- OmniauthCallbacksController#link_identity
- GroupPolicy#lookup_access_level!

Add columns to store project creation settings

Add project creation level column in groups
 and default project creation column in application settings

Remove obsolete line from schema

Update migration with project_creation_level column existence check

Rename migrations to avoid conflicts

Update migration methods

Update migration method

Include a new policy in Clusterables
(projects and groups), which checks if another cluster
can be added

clusterable_has_cluster? and multiple_clusters_available
private methods will be overriden in EE

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/34758

- we now use the hierarchy class also for epics
- also rename supports_nested_groups? into supports_nested_objects?
  - move it to a concern

Signed-off-by: Rémy Coutable <remy@rymai.me>

- maintainer for group can read, create, update, and admin cluster
- project user, at any level, cannot do anything with group cluster

This is more idiomatic than checking membership explicitly.

Enable frozen string in:

* app/presenters
* app/policies

Partially addresses #47424.

This allows us to check specific abilities in views, while still
enabling/disabling them at once.