From b5a5ad2a0ec79da99f8df479a97e018c92c1e9f2 Mon Sep 17 00:00:00 2001 From: Vanessa Date: Sat, 11 Mar 2023 15:24:18 +1000 Subject: [PATCH] Enterprise bug fixes for the week of Mar 06, 2023 (#35459) Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com> --- .../managing-projects-using-jira.md | 22 ++++++++++++------- .../viewing-your-github-copilot-usage.md | 2 +- 2 files changed, 15 insertions(+), 9 deletions(-) diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md index c9f9bcaa0ba7..bc294a0d519b 100644 --- a/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md +++ b/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md @@ -19,17 +19,23 @@ shortTitle: Project management with Jira --- ## Connecting Jira to a {% data variables.product.prodname_enterprise %} organization -1. Sign into your {% data variables.product.prodname_enterprise %} account at `http[s]://[hostname]/login`. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner. -2. Click on your profile icon under the {% data variables.product.prodname_dotcom %} logo and select the organization you would like to connect with Jira. -3. Click on the **Edit _organization name_ settings** link. -4. In the left sidebar, under **Developer settings**, click **OAuth Apps**. -5. Click on the **Register new application** button. -6. Fill in the application settings: +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.oauth_apps %} +1. Click **New {% data variables.product.prodname_oauth_app %}**. + + {% note %} + + **Note:** If you haven't created an app before, this button will say, **Register an application**. + + {% endnote %} +1. Fill in the application settings: - In the **Application name** field, type "Jira" or any name you would like to use to identify the Jira instance. - In the **Homepage URL** field, type the full URL of your Jira instance. - In the **Authorization callback URL** field, type the full URL of your Jira instance. -7. Click **Register application**. -8. At the top of the page, note the **Client ID** and **Client Secret**. You will need these for configuring your Jira instance. +1. Click **Register application**. +1. At the top of the page, note the **Client ID** and **Client Secret**. You will need these for configuring your Jira instance. ## Jira instance configuration diff --git a/content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md b/content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md index d6c6fd5da7da..682814d8cfa9 100644 --- a/content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md +++ b/content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md @@ -13,7 +13,7 @@ shortTitle: View your usage ## About your {% data variables.product.prodname_copilot %} usage -You can view usage information for {% data variables.product.prodname_copilot %} in your {% ifversion ghec %}enterprise, broken down by organization, or in your{% else %} organization{% endif %}, broken down by seat assignment status. {% ifversion ghec %}At the enterprise level, this information includes the number of seats assigned in each organization, and the total spending associated with each organization, for the current billing cycle.{% endif %} At the organization level, this information includes the total number of seats, seats carried over from the previous billing cycle, new seats added during the current cycle, and seats to be removed at the end of the current cycle. +You can view usage information for {% data variables.product.prodname_copilot %} in your {% ifversion ghec %}enterprise, broken down by organization, or in your{% endif %} organization, broken down by seat assignment status. {% ifversion ghec %}At the enterprise level, this information includes the number of seats assigned in each organization, and the total spending associated with each organization, for the current billing cycle.{% endif %} At the organization level, this information includes the total number of seats, seats carried over from the previous billing cycle, new seats added during the current cycle, and seats to be removed at the end of the current cycle. If an organization admin has assigned one or more seats partway through the current billing cycle, the enterprise-level information will display a decimal number of seats. For example, if the organization started the billing cycle with 3 seats assigned, and then assigned an additional seat half way through the cycle, the seat usage information will display 3.5 seats. The "3" representing the seats assigned at the start of the cycle, and the "0.5" representing the additional seat assigned halfway through the cycle.