diff options
author | michaelbirnstiehl <michael.birnstiehl@sonarsource.com> | 2020-01-08 14:19:49 -0600 |
---|---|---|
committer | SonarTech <sonartech@sonarsource.com> | 2020-02-10 20:46:15 +0100 |
commit | 5ac4c80c8438a31aca58b0ac377a0ec948d68ded (patch) | |
tree | 35ea1b56007b09cf00a5d75bd483384e8e8fcf74 /server/sonar-docs/src/pages/project-administration | |
parent | 04237dba5156dca631d687c4ce6b88de60eef14b (diff) | |
download | sonarqube-5ac4c80c8438a31aca58b0ac377a0ec948d68ded.tar.gz sonarqube-5ac4c80c8438a31aca58b0ac377a0ec948d68ded.zip |
SONAR-12905 Update paths in the docs for new projects UI
Diffstat (limited to 'server/sonar-docs/src/pages/project-administration')
4 files changed, 13 insertions, 13 deletions
diff --git a/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md b/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md index 96cb28548e0..dc8f137061a 100644 --- a/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md +++ b/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md @@ -12,7 +12,7 @@ If {instance}'s results aren't relevant, no one will want to use it. That's why * exclude files/directories from Duplications detection but analyze all other aspects * exclude files/directories from Coverage calculations but analyze all other aspects -You can make these changes globally or at a project level. At both levels, the navigation path is **Administration > General Settings > Analysis Scope**. +You can make these changes globally or at a project level. At the global level, the navigation path is **Administration > General Settings > Analysis Scope**. At the project level, the navigation path is **Project Settings > General Settings > Analysis Scope** ## Patterns diff --git a/server/sonar-docs/src/pages/project-administration/new-code-period.md b/server/sonar-docs/src/pages/project-administration/new-code-period.md index 2d710648511..804532d7a3b 100644 --- a/server/sonar-docs/src/pages/project-administration/new-code-period.md +++ b/server/sonar-docs/src/pages/project-administration/new-code-period.md @@ -15,7 +15,7 @@ You can set the global New Code Period to the following: * **Number of days** – You can specify a number of days for a floating New Code Period. For example, setting **Number of Days** to 30 creates a floating New Code Period beginning 30 days from the current date. ## Setting a project-level New Code Period -You can override the global New Code Period by setting a project-level New Code Period from the project page at **Administration > New Code Period**. For [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/), this will be the default New Code Period for all of the project's branches. +You can override the global New Code Period by setting a project-level New Code Period from the project page at **Project Settings > New Code Period**. For [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/), this will be the default New Code Period for all of the project's branches. You can set a project's New Code Period to the following: diff --git a/server/sonar-docs/src/pages/project-administration/project-settings.md b/server/sonar-docs/src/pages/project-administration/project-settings.md index 3988ef4bd31..2c28bce1b24 100644 --- a/server/sonar-docs/src/pages/project-administration/project-settings.md +++ b/server/sonar-docs/src/pages/project-administration/project-settings.md @@ -9,7 +9,7 @@ Project tags allow you to categorize and group projects for easier selection on ## Administration Items -Project administration is accessible through the **Administration** menu of each project. +Project administration is accessible through the **Project Settings** menu of each project. Only project administrators can access project's settings (see [Authorization](/instance-administration/security/)). @@ -19,33 +19,33 @@ A project is automatically added at its first analysis. Note that you can also [ ### Analysis Report Processing -A project-level Background Tasks page is available at **Administration > Background Tasks** to allow project administrators to check their projects' processing. It offers analysis report details and logs. +A project-level Background Tasks page is available at **Project Settings > Background Tasks** to allow project administrators to check their projects' processing. It offers analysis report details and logs. ### Deleting a Project #### Deleting a Single Project -You can delete a project through **Administration > Deletion**. +You can delete a project through **Project Settings > Deletion**. #### Deleting Multiple Projects -You can also delete multiple projects simultaneously from the global **Administration > Projects > Management**. +You can also delete multiple projects simultaneously from the global **Project Settings > Projects > Management**. ### Updating the Project Key -The project key can be updated (without losing the history on the project) at **Administration > Update Key**. +The project key can be updated (without losing the history on the project) at **Project Settings > Update Key**. The new key must contain at least one non-digit character. Allowed characters are: 'a' through 'z', 'A' through 'Z', '-' (dash), '\_' (underscore), '.' (dot), ':' (colon) and digits '0' to '9'. ### Default Issue Assignee -When new issues are created during an analysis, they are assigned to the last committer where the issue was raised. When it is not possible to identify the last committer, issues can be assigned to a default assignee, at ]Administration > General Settings > Issues](/#sonarqube-admin#/admin/settings). +When new issues are created during an analysis, they are assigned to the last committer where the issue was raised. When it is not possible to identify the last committer, issues can be assigned to a default assignee, at [Administration > General Settings > Issues](/#sonarqube-admin#/admin/settings). ### Setting Quality Gate and Quality Profiles Project administrators can select which ... -* Quality profiles (go to **Administration > Quality Profiles**) -* Quality gate (go to **Administration > Quality Gate**) +* Quality profiles (go to **Project Settings > Quality Profiles**) +* Quality gate (go to **Project Settings > Quality Gate**) ... to use on their project. @@ -55,4 +55,4 @@ See [Narrowing the Focus](/project-administration/narrowing-the-focus/). ### Customizing Links -On top of standard links which may only be set as [Analysis Parameters](/analysis/analysis-parameters/), additional custom links can be added through the web interface (under **Administration > Links**). Those links will then be displayed in the [Project Page](/user-guide/project-page/). +On top of standard links which may only be set as [Analysis Parameters](/analysis/analysis-parameters/), additional custom links can be added through the web interface (under **Project Settings > Links**). Those links will then be displayed in the [Project Page](/user-guide/project-page/). diff --git a/server/sonar-docs/src/pages/project-administration/webhooks.md b/server/sonar-docs/src/pages/project-administration/webhooks.md index 64e9a4ef5e2..4556590d9ed 100644 --- a/server/sonar-docs/src/pages/project-administration/webhooks.md +++ b/server/sonar-docs/src/pages/project-administration/webhooks.md @@ -13,7 +13,7 @@ The HTTP(S) call: ## Configuration -You can configure up to 10 webhooks in in **Administration > Webhooks**. +You can configure up to 10 webhooks at the project level in **Project Settings > Webhooks**. An additional set of 10 webhooks can be configured at the global level in **Administration > Configuration > Webhooks**. @@ -106,7 +106,7 @@ After you've configured your server to receive payloads, you want to be sure tha To set your secret in {instance}: -1. From the project or organization where you're securing your webhooks, navigate to the webhooks settings at **Administration > webhooks** +1. From the project or organization where you're securing your webhooks, navigate to the webhooks settings at **Project Settings > Webhooks** 1. You can either click **Create** to create a new webhook or click an existing webhook's settings drop-down and click **Update**. 1. Enter a random string in the **Secret** text box. This is used as the key to generate the HMAC hex digest value in the `X-Sonar-Webhook-HMAC-SHA256` header. 1. Click **Update**. |