From 0cee22bfbd89ba605f91463d2342f5bf6bc7bed5 Mon Sep 17 00:00:00 2001 From: Sarita Iyer <66540150+saritai@users.noreply.github.com> Date: Mon, 1 Jun 2026 17:08:32 -0400 Subject: [PATCH 1/2] remove beta info for jira integration (#61526) Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .../cloud-agent/integrate-cloud-agent-with-jira.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/copilot/how-tos/use-copilot-agents/cloud-agent/integrate-cloud-agent-with-jira.md b/content/copilot/how-tos/use-copilot-agents/cloud-agent/integrate-cloud-agent-with-jira.md index 5b0a7a4bfa21..a775507514ab 100644 --- a/content/copilot/how-tos/use-copilot-agents/cloud-agent/integrate-cloud-agent-with-jira.md +++ b/content/copilot/how-tos/use-copilot-agents/cloud-agent/integrate-cloud-agent-with-jira.md @@ -24,9 +24,8 @@ The {% data variables.product.prodname_copilot %} integration in Jira allows you ## Prerequisites * You must have a {% data variables.product.github %} account with access to {% data variables.product.prodname_copilot_short %} through a paid {% data variables.product.prodname_copilot_short %} plan. -* You must have a Jira Cloud account with the following AI features enabled for your organization: +* You must have a Jira Cloud account with the following AI feature enabled for your organization: * **Jira must be an AI-enabled app** and Rovo must be activated. See [Activate AI for apps](https://support.atlassian.com/organization-administration/docs/activate-atlassian-intelligence-for-products) in the Atlassian documentation. - * **Beta AI features** must be turned on. See [Control access to beta AI features](https://support.atlassian.com/organization-administration/docs/control-access-to-beta-ai-features/) in the Atlassian documentation. * Installation and authentication must be completed for both Jira and {% data variables.product.github %}. > [!NOTE] @@ -148,7 +147,6 @@ If you run into problems, try the following solutions. In Jira, check your Atlassian Administration settings for your organization are set as follows. 1. Jira is an AI-enabled app, see [Activate AI for apps](https://support.atlassian.com/organization-administration/docs/activate-atlassian-intelligence-for-products) in the Atlassian documentation. -1. Beta AI features are enabled, see [Control access to beta AI features](https://support.atlassian.com/organization-administration/docs/control-access-to-beta-ai-features/) in the Atlassian documentation. ### You can see the {% data variables.copilot.copilot_cloud_agent %} but it is not possible to assign it to a Jira work item From c04b81516efeab52042000a4f896640865f5237e Mon Sep 17 00:00:00 2001 From: Joe Clark <31087804+jc-clark@users.noreply.github.com> Date: Mon, 1 Jun 2026 14:49:51 -0700 Subject: [PATCH 2/2] Add org-level runner configuration docs for CCR and CCA (#61527) Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .../set-up-copilot/configure-runners.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/content/copilot/how-tos/copilot-on-github/set-up-copilot/configure-runners.md b/content/copilot/how-tos/copilot-on-github/set-up-copilot/configure-runners.md index 2f2bcd19ceb1..403f80bef53d 100644 --- a/content/copilot/how-tos/copilot-on-github/set-up-copilot/configure-runners.md +++ b/content/copilot/how-tos/copilot-on-github/set-up-copilot/configure-runners.md @@ -71,3 +71,21 @@ By default, {% data variables.copilot.copilot_code-review_short %} runs on a sta runs-on: ubuntu-4-core # ... ``` + +## Configure runners at the organization level + +Organization owners can set a default runner type for {% data variables.copilot.copilot_code-review_short %} and {% data variables.copilot.copilot_cloud_agent %} across all repositories in the organization, and control whether individual repositories can override this default. + +> [!NOTE] +> The organization-level runner type applies to both {% data variables.copilot.copilot_code-review_short %} and {% data variables.copilot.copilot_cloud_agent %}. Repositories can still override the organization default using `copilot-setup-steps.yml` unless you disable **Allow repositories to customize the runner type**. For more information, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/configure-runner-for-coding-agent#preventing-repositories-from-customizing-the-runner-type). + +This is useful if your organization requires all code reviews and {% data variables.copilot.copilot_cloud_agent_short %} tasks to run on specific runners, for example, to use larger runners for better performance or self-hosted runners that have access to internal resources. + +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +1. In the sidebar, under "Code, planning, and automation," click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, and then click **Runner type**. +1. Next to "Runner type configuration," click {% octicon "pencil" aria-label="Edit" %}. +1. In the "Edit runner type" dialog, select the runner type to use by default across your organization, then click **Save runner selection**. + * **Standard {% data variables.product.prodname_dotcom %} runner**: {% data variables.copilot.copilot_code-review_short %} and {% data variables.copilot.copilot_cloud_agent %} will use the standard {% data variables.product.prodname_dotcom %}-hosted runner. + * **Labeled runner**: {% data variables.copilot.copilot_code-review_short %} and {% data variables.copilot.copilot_cloud_agent %} will use a runner matching the label you specify. +1. Optionally, to prevent individual repositories from overriding the organization-level runner configuration using their `copilot-setup-steps.yml` file, disable **Allow repositories to customize the runner type**.