Add latest changes from gitlab-org/gitlab@14-10-stable-eev14.10.0-rc42

2 files changed, 19 insertions, 7 deletions

diff --git a/doc/ci/jobs/ci_job_token.md b/doc/ci/jobs/ci_job_token.md
index b0002f559ba..8e5c8c8ab45 100644
--- a/doc/ci/jobs/ci_job_token.md
+++ b/doc/ci/jobs/ci_job_token.md
@@ -83,8 +83,7 @@ to be accessed by authenticating with the current project's job token. By defaul
 the token scope only allows access to the same project where the token comes from.
 Other projects can be added and removed by maintainers with access to both projects.
 
-This setting is enabled by default for all new projects, and disabled by default in projects
-created before GitLab 14.1. It is strongly recommended that project maintainers enable this
+This setting is disabled by default for all new projects. It is recommended that project maintainers enable this
 setting at all times, and configure the allowlist for cross-project access if needed.
 
 For example, when the setting is enabled, jobs in a pipeline in project `A` have
diff --git a/doc/ci/jobs/index.md b/doc/ci/jobs/index.md
index 4fa251eb3cf..b8129e1cf18 100644
--- a/doc/ci/jobs/index.md
+++ b/doc/ci/jobs/index.md
@@ -43,6 +43,18 @@ Clicking an individual job shows you its job log, and allows you to:
 - Retry the job.
 - Erase the job log.
 
+### View all jobs in a project
+
+> - An improved view was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/293862) in GitLab 14.10, [with a flag](../../administration/feature_flags.md) named `jobs_table_vue`. Disabled by default.
+> - The job status filter was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82539) in GitLab 14.10, [with a flag](../../administration/feature_flags.md) named `jobs_table_vue_search`. Disabled by default.
+
+To view the full list of jobs that ran in a project:
+
+1. On the top bar, select **Menu > Projects** and find the project.
+1. On the left sidebar, select **CI/CD > Jobs**.
+
+You can filter the list by [job status](#the-order-of-jobs-in-a-pipeline).
+
 ## See why a job failed
 
 When a pipeline fails or is allowed to fail, there are several places where you
@@ -63,9 +75,9 @@ You can also see the reason it failed on the Job detail page.
 The order of jobs in a pipeline depends on the type of pipeline graph.
 
 - For [full pipeline graphs](../pipelines/index.md#view-full-pipeline-graph), jobs are sorted by name.
-- For [pipeline mini graphs](../pipelines/index.md#pipeline-mini-graphs), jobs are sorted by severity and then by name.
+- For [pipeline mini graphs](../pipelines/index.md#pipeline-mini-graphs), jobs are sorted by status, and then by name.
 
-The order of severity is:
+The job status order is:
 
 - failed
 - warning
@@ -84,6 +96,9 @@ For example:
 
 ## Job name limitations
 
+> - [Enabled 255-character job length on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/342800) in GitLab 14.5.
+> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/344665) in GitLab 14.10. [Feature flag `ci_validate_job_length`](https://gitlab.com/gitlab-org/gitlab/-/issues/344665) removed.
+
 You can't use these keywords as job names:
 
 - `image`
@@ -99,9 +114,7 @@ You can't use these keywords as job names:
 - `false`
 - `nil`
 
-Job names must be 255 characters or less. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/342800)
-in GitLab 14.5, [with a feature flag](../../administration/feature_flags.md) named `ci_validate_job_length`.
-Enabled by default. To disable it, ask an administrator to [disable the feature flag](../../administration/feature_flags.md).
+Job names must be 255 characters or fewer.
 
 Use unique names for your jobs. If multiple jobs have the same name,
 only one is added to the pipeline, and it's difficult to predict which one is chosen.