diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-15 18:15:04 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-15 18:15:04 +0300 |
commit | 78cfc7cf4afe0c7ffb72b8a9522b07873cd36820 (patch) | |
tree | 8cc90263a1593ddad6d9f817273fdcffdd10c9f6 /doc/user | |
parent | 524e97262236b70abe4399faef040f4298c31d38 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
-rw-r--r-- | doc/user/clusters/agent/troubleshooting.md | 2 | ||||
-rw-r--r-- | doc/user/permissions.md | 17 | ||||
-rw-r--r-- | doc/user/search/index.md | 25 |
3 files changed, 20 insertions, 24 deletions
diff --git a/doc/user/clusters/agent/troubleshooting.md b/doc/user/clusters/agent/troubleshooting.md index d5777267582..2c9f98b7c45 100644 --- a/doc/user/clusters/agent/troubleshooting.md +++ b/doc/user/clusters/agent/troubleshooting.md @@ -11,7 +11,7 @@ When you are using the GitLab Agent for Kubernetes, you might experience issues You can start by viewing the service logs: ```shell -kubectl logs -f -l=app=gitlab-kubernetes-agent -n gitlab-kubernetes-agent +kubectl logs -f -l=app=gitlab-agent -n gitlab-kubernetes-agent ``` If you are a GitLab administrator, you can also view the [GitLab Agent Server logs](../../../administration/clusters/kas.md#troubleshooting). diff --git a/doc/user/permissions.md b/doc/user/permissions.md index 36c81f8ca9b..a00ac13c87b 100644 --- a/doc/user/permissions.md +++ b/doc/user/permissions.md @@ -33,27 +33,14 @@ usernames. A GitLab administrator can configure the GitLab instance to ## Project members permissions -> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/219299) in GitLab 14.8, personal namespace owners appear with Owner role in new projects in their namespace. Introduced [with a flag](../administration/feature_flags.md) named `personal_project_owner_with_owner_access`. Disabled by default. - -FLAG: -On self-managed GitLab, personal namespace owners appearing with the Owner role in new projects in their namespace is disabled. To make it available, -ask an administrator to [enable the feature flag](../administration/feature_flags.md) named `personal_project_owner_with_owner_access`. -The feature is not ready for production use. -On GitLab.com, this feature is not available. - A user's role determines what permissions they have on a project. The Owner role provides all permissions but is available only: - For group owners. The role is inherited for a group's projects. - For Administrators. -Personal [namespace](group/index.md#namespaces) owners: - -- Are displayed as having the Maintainer role on projects in the namespace, but have the same permissions as a user with the Owner role. -- (Disabled by default) In GitLab 14.8 and later, for new projects in the namespace, are displayed as having the Owner role. - -For more information about how to manage project members, see -[members of a project](project/members/index.md). +Personal namespace owners have the same permissions as an Owner, but are displayed with the Maintainer role on projects created in their personal namespace. +For more information, see [projects members documentation](project/members/index.md). The following table lists project permissions available for each role: diff --git a/doc/user/search/index.md b/doc/user/search/index.md index 408b55a6fe7..0a799843d3c 100644 --- a/doc/user/search/index.md +++ b/doc/user/search/index.md @@ -32,24 +32,33 @@ in the search field in the upper right corner: ### Filter issue and merge request lists -> - Filter by Epics was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/195704) in GitLab Ultimate 12.9. -> - Filter by child Epics was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9029) in GitLab Ultimate 13.0. -> - Filter by Iterations was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/118742) in GitLab 13.6. Moved to GitLab Premium in 13.9. +> - Filtering by epics was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/195704) in GitLab 12.9. +> - Filtering by child epics was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9029) in GitLab 13.0. +> - Filtering by iterations was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/118742) in GitLab 13.6. Moved from GitLab Ultimate to Premium in 13.9. +> - Filtering by type was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/322755) in GitLab 13.10 [with a flag](../../administration/feature_flags.md) named `vue_issues_list`. Disabled by default. Follow these steps to filter the **Issues** and **Merge requests** list pages in projects and groups: 1. Click in the field **Search or filter results...**. 1. In the dropdown menu that appears, select the attribute you wish to filter by: - - Author - Assignee - - [Milestone](../project/milestones/index.md) + - Author + - Confidential + - [Epic and child Epic](../group/epics/index.md) (available only for the group the Epic was created, not for [higher group levels](https://gitlab.com/gitlab-org/gitlab/-/issues/233729)). - [Iteration](../group/iterations/index.md) - - Release - [Label](../project/labels.md) + - [Milestone](../project/milestones/index.md) - My-reaction - - Confidential - - [Epic and child Epic](../group/epics/index.md) (available only for the group the Epic was created, not for [higher group levels](https://gitlab.com/gitlab-org/gitlab/-/issues/233729)). + - Release + - Type + + FLAG: + On self-managed GitLab, by default filtering by type is not available. + To make it available per group, ask an administrator to [enable the feature flag](../../administration/feature_flags.md) named `vue_issues_list`. + On GitLab.com, this feature is not available. + + - Weight - Search for this text 1. Select or type the operator to use for filtering the attribute. The following operators are available: |