diff --git a/assets/images/help/issues/issue-type.png b/assets/images/help/issues/issue-type.png
new file mode 100644
index 000000000000..3da77552cbe0
Binary files /dev/null and b/assets/images/help/issues/issue-type.png differ
diff --git a/assets/images/help/issues/sub-issue.png b/assets/images/help/issues/sub-issue.png
new file mode 100644
index 000000000000..872341db72cf
Binary files /dev/null and b/assets/images/help/issues/sub-issue.png differ
diff --git a/assets/images/help/projects-v2/example-board.png b/assets/images/help/projects-v2/example-board.png
index 3d52275476e1..6341281a07d0 100644
Binary files a/assets/images/help/projects-v2/example-board.png and b/assets/images/help/projects-v2/example-board.png differ
diff --git a/assets/images/help/projects-v2/example-roadmap.png b/assets/images/help/projects-v2/example-roadmap.png
index 5ba93a957172..a2551a1c4330 100644
Binary files a/assets/images/help/projects-v2/example-roadmap.png and b/assets/images/help/projects-v2/example-roadmap.png differ
diff --git a/assets/images/help/projects-v2/example-table.png b/assets/images/help/projects-v2/example-table.png
index ebce838884a0..c5a3c16f9a1d 100644
Binary files a/assets/images/help/projects-v2/example-table.png and b/assets/images/help/projects-v2/example-table.png differ
diff --git a/content/copilot/reference/ai-models/model-comparison.md b/content/copilot/reference/ai-models/model-comparison.md
index 5b33434b11f9..9fcc2905d3cc 100644
--- a/content/copilot/reference/ai-models/model-comparison.md
+++ b/content/copilot/reference/ai-models/model-comparison.md
@@ -21,33 +21,37 @@ contentType: reference
### Recommended models by task
+{% data reusables.copilot.grok-promo-period %}
+
Use this table to find a suitable model quickly, see more detail in the sections below.
-| Model | Task area | Excels at (primary use case) | Additional capabilities | Further reading |
-|-------|-----------|-------------------------------|--------------------------|------------------|
-| {% data variables.copilot.copilot_gpt_41 %} | General-purpose coding and writing | Fast, accurate code completions and explanations | Agent mode, vision | [{% data variables.copilot.copilot_gpt_41 %} model card](https://openai.com/index/gpt-4-1/)|
-| {% data variables.copilot.copilot_gpt_5_mini %} | Deep reasoning and debugging | Well-defined tasks and precise prompts | Reasoning | Not available |
-| {% data variables.copilot.copilot_gpt_5 %} | Deep reasoning and debugging | Multi-step problem solving and architecture-level code analysis | Reasoning | [{% data variables.copilot.copilot_gpt_5 %} model card](https://cdn.openai.com/pdf/8124a3ce-ab78-4f06-96eb-49ea29ffb52f/gpt5-system-card-aug7.pdf) |
-| {% data variables.copilot.copilot_o3 %} | Deep reasoning and debugging | Multi-step problem solving and architecture-level code analysis | Reasoning | [{% data variables.copilot.copilot_o3 %} model card](https://openai.com/index/o3-o4-mini-system-card/) |
-| {% data variables.copilot.copilot_o4_mini %} | Fast help with simple or repetitive tasks | Fast, reliable answers to lightweight coding questions | Lower latency | [{% data variables.copilot.copilot_o4_mini %} model card](https://openai.com/index/o3-o4-mini-system-card/) |
-| {% data variables.copilot.copilot_claude_opus_41 %} | Deep reasoning and debugging | Complex problem-solving challenges, sophisticated reasoning | Reasoning, vision | [{% data variables.copilot.copilot_claude_opus_41 %} model card](https://assets.anthropic.com/m/4c024b86c698d3d4/original/Claude-4-1-System-Card.pdf) |
-| {% data variables.copilot.copilot_claude_opus %} | Deep reasoning and debugging | Complex problem-solving challenges, sophisticated reasoning | Reasoning, vision | [{% data variables.copilot.copilot_claude_opus %} model card](https://www-cdn.anthropic.com/6be99a52cb68eb70eb9572b4cafad13df32ed995.pdf) |
-| {% data variables.copilot.copilot_claude_sonnet_35 %} | Fast help with simple or repetitive tasks | Quick responses for code, syntax, and documentation | Agent mode, vision | [{% data variables.copilot.copilot_claude_sonnet_35 %} model card](https://www-cdn.anthropic.com/fed9cc193a14b84131812372d8d5857f8f304c52/Model_Card_Claude_3_Addendum.pdf) |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} | Deep reasoning and debugging | Structured reasoning across large, complex codebases | Agent mode, vision | [{% data variables.copilot.copilot_claude_sonnet_37 %} model card](https://assets.anthropic.com/m/785e231869ea8b3b/original/claude-3-7-sonnet-system-card.pdf) |
-| {% data variables.copilot.copilot_claude_sonnet_40 %} | Deep reasoning and debugging | Performance and practicality, perfectly balanced for coding workflows | Agent mode, vision | [{% data variables.copilot.copilot_claude_sonnet_40 %} model card](https://www-cdn.anthropic.com/6be99a52cb68eb70eb9572b4cafad13df32ed995.pdf) |
-| {% data variables.copilot.copilot_gemini_25_pro %} | Deep reasoning and debugging | Complex code generation, debugging, and research workflows | Reasoning, vision | [{% data variables.copilot.copilot_gemini_25_pro %} model card](https://storage.googleapis.com/model-cards/documents/gemini-2.5-pro.pdf) |
-| {% data variables.copilot.copilot_gemini_flash %} | Working with visuals (diagrams, screenshots) | Real-time responses and visual reasoning for UI and diagram-based tasks | Vision | [{% data variables.copilot.copilot_gemini_flash %} model card](https://storage.googleapis.com/model-cards/documents/gemini-2-flash.pdf) |
+| Model | Task area | Excels at (primary use case) | Additional capabilities | Further reading |
+|-------------------------------------------------------|-----------|-------------------------------|-------------------------|------------------|
+| {% data variables.copilot.copilot_gpt_41 %} | General-purpose coding and writing | Fast, accurate code completions and explanations | Agent mode, vision | [{% data variables.copilot.copilot_gpt_41 %} model card](https://openai.com/index/gpt-4-1/)|
+| {% data variables.copilot.copilot_gpt_5_mini %} | Deep reasoning and debugging | Well-defined tasks and precise prompts | Reasoning, vision | Not available |
+| {% data variables.copilot.copilot_gpt_5 %} | Deep reasoning and debugging | Multi-step problem solving and architecture-level code analysis | Reasoning | [{% data variables.copilot.copilot_gpt_5 %} model card](https://cdn.openai.com/pdf/8124a3ce-ab78-4f06-96eb-49ea29ffb52f/gpt5-system-card-aug7.pdf) |
+| {% data variables.copilot.copilot_o3 %} | Deep reasoning and debugging | Multi-step problem solving and architecture-level code analysis | Reasoning | [{% data variables.copilot.copilot_o3 %} model card](https://openai.com/index/o3-o4-mini-system-card/) |
+| {% data variables.copilot.copilot_o4_mini %} | Fast help with simple or repetitive tasks | Fast, reliable answers to lightweight coding questions | Lower latency | [{% data variables.copilot.copilot_o4_mini %} model card](https://openai.com/index/o3-o4-mini-system-card/) |
+| {% data variables.copilot.copilot_claude_opus_41 %} | Deep reasoning and debugging | Complex problem-solving challenges, sophisticated reasoning | Reasoning, vision | [{% data variables.copilot.copilot_claude_opus_41 %} model card](https://assets.anthropic.com/m/4c024b86c698d3d4/original/Claude-4-1-System-Card.pdf) |
+| {% data variables.copilot.copilot_claude_opus %} | Deep reasoning and debugging | Complex problem-solving challenges, sophisticated reasoning | Reasoning, vision | [{% data variables.copilot.copilot_claude_opus %} model card](https://www-cdn.anthropic.com/6be99a52cb68eb70eb9572b4cafad13df32ed995.pdf) |
+| {% data variables.copilot.copilot_claude_sonnet_35 %} | Fast help with simple or repetitive tasks | Quick responses for code, syntax, and documentation | Agent mode, vision | [{% data variables.copilot.copilot_claude_sonnet_35 %} model card](https://www-cdn.anthropic.com/fed9cc193a14b84131812372d8d5857f8f304c52/Model_Card_Claude_3_Addendum.pdf) |
+| {% data variables.copilot.copilot_claude_sonnet_37 %} | Deep reasoning and debugging | Structured reasoning across large, complex codebases | Agent mode, vision | [{% data variables.copilot.copilot_claude_sonnet_37 %} model card](https://assets.anthropic.com/m/785e231869ea8b3b/original/claude-3-7-sonnet-system-card.pdf) |
+| {% data variables.copilot.copilot_claude_sonnet_40 %} | Deep reasoning and debugging | Performance and practicality, perfectly balanced for coding workflows | Agent mode, vision | [{% data variables.copilot.copilot_claude_sonnet_40 %} model card](https://www-cdn.anthropic.com/6be99a52cb68eb70eb9572b4cafad13df32ed995.pdf) |
+| {% data variables.copilot.copilot_gemini_25_pro %} | Deep reasoning and debugging | Complex code generation, debugging, and research workflows | Reasoning, vision | [{% data variables.copilot.copilot_gemini_25_pro %} model card](https://storage.googleapis.com/model-cards/documents/gemini-2.5-pro.pdf) |
+| {% data variables.copilot.copilot_gemini_flash %} | Working with visuals (diagrams, screenshots) | Real-time responses and visual reasoning for UI and diagram-based tasks | Vision | [{% data variables.copilot.copilot_gemini_flash %} model card](https://storage.googleapis.com/model-cards/documents/gemini-2-flash.pdf) |
+| {% data variables.copilot.copilot_grok_code %} | General-purpose coding and writing | Fast, accurate code completions and explanations | Agent mode, vision | [{% data variables.copilot.copilot_grok_code %} model card](https://data.x.ai/2025-08-20-grok-4-model-card.pdf)|
## Task: General-purpose coding and writing
Use these models for common development tasks that require a balance of quality, speed, and cost efficiency. These models are a good default when you don't have specific requirements.
-| Model | Why it's a good fit |
-|-------|---------------------|
-| {% data variables.copilot.copilot_gpt_41 %} | Reliable default for most coding and writing tasks. Fast, accurate, and works well across languages and frameworks. |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} | Produces clear, structured output. Follows formatting instructions and maintains consistent style. |
-| {% data variables.copilot.copilot_gemini_flash %} | Fast and cost-effective. Well suited for quick questions, short code snippets, and lightweight writing tasks. |
-| {% data variables.copilot.copilot_o4_mini %} | Optimized for speed and cost efficiency. Ideal for real-time suggestions with low usage overhead. |
+| Model | Why it's a good fit |
+|-------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| {% data variables.copilot.copilot_gpt_41 %} | Reliable default for most coding and writing tasks. Fast, accurate, and works well across languages and frameworks. |
+| {% data variables.copilot.copilot_claude_sonnet_37 %} | Produces clear, structured output. Follows formatting instructions and maintains consistent style. |
+| {% data variables.copilot.copilot_gemini_flash %} | Fast and cost-effective. Well suited for quick questions, short code snippets, and lightweight writing tasks. |
+| {% data variables.copilot.copilot_o4_mini %} | Optimized for speed and cost efficiency. Ideal for real-time suggestions with low usage overhead. |
+| {% data variables.copilot.copilot_grok_code %} | Specialized for coding tasks. Performs well on code generation, and debugging across multiple languages. |
### When to use these models
diff --git a/content/copilot/reference/ai-models/model-hosting.md b/content/copilot/reference/ai-models/model-hosting.md
index cff17d2aeaf8..52c95a870eb9 100644
--- a/content/copilot/reference/ai-models/model-hosting.md
+++ b/content/copilot/reference/ai-models/model-hosting.md
@@ -63,3 +63,22 @@ Used for:
To provide better service quality and reduce latency, {% data variables.product.github %} uses [prompt caching](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance#customer_data_retention_and_achieving_zero_data_retention).
When using {% data variables.copilot.copilot_gemini %} models, input prompts and output completions continue to run through {% data variables.product.prodname_copilot %}'s content filters for public code matching, when applied, along with those for harmful or offensive content.
+
+## xAI models
+
+{% data reusables.copilot.grok-promo-period %}
+
+{% data variables.copilot.copilot_grok_code %} is hosted by xAI when used in {% data variables.product.prodname_copilot %}.
+
+xAI operates {% data variables.copilot.copilot_grok_code %} in {% data variables.product.prodname_copilot %} under a zero data retention API policy. This means xAI commits that user content (both inputs sent to the model and outputs generated by the model):
+
+Will **not** be:
+* Logged for any purpose, including human review
+* Saved to disk or retained in any form, including as metadata
+* Accessible by xAI personnel
+
+Will **only**:
+* Exist temporarily in RAM for the minimum time required to process and respond to each request
+* Be immediately deleted from memory once the response is delivered
+
+When using xAI, input prompts and output completions continue to run through {% data variables.product.prodname_copilot %}'s content filters for public code matching, when applied, along with those for harmful or offensive content.
diff --git a/content/copilot/reference/ai-models/supported-models.md b/content/copilot/reference/ai-models/supported-models.md
index 95d991afaf74..7bf94e1db31a 100644
--- a/content/copilot/reference/ai-models/supported-models.md
+++ b/content/copilot/reference/ai-models/supported-models.md
@@ -33,23 +33,26 @@ For all AI models, input prompts and output completions run through {% data vari
This table lists the AI models available in {% data variables.product.prodname_copilot_short %}, along with their release status and availability in different modes.
+{% data reusables.copilot.grok-promo-period %}
+
{% rowheaders %}
-| Model name | Provider | Release status | Agent mode | Ask mode | Edit mode |
-|----------------------------------------------------------------|----------|--------------|------------|----------------------|---------------|
-| {% data variables.copilot.copilot_gpt_41 %} | OpenAI | GA | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gpt_5_mini %} | OpenAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gpt_5 %} | OpenAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_o3 %} | OpenAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_o4_mini %} | OpenAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| Model name | Provider | Release status | Agent mode | Ask mode | Edit mode |
+|----------------------------------------------------------------|-----------|------------|---------------------------------------------|----------------------|---------------|
+| {% data variables.copilot.copilot_gpt_41 %} | OpenAI | GA | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gpt_5_mini %} | OpenAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gpt_5 %} | OpenAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_o3 %} | OpenAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_o4_mini %} | OpenAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
| {% data variables.copilot.copilot_claude_opus_41 %} | Anthropic | {% data variables.release-phases.public_preview_caps %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
| {% data variables.copilot.copilot_claude_opus %} | Anthropic | GA | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
| {% data variables.copilot.copilot_claude_sonnet_35 %} | Anthropic | GA | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
| {% data variables.copilot.copilot_claude_sonnet_37 %} | Anthropic | GA | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | Anthropic | GA | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
| {% data variables.copilot.copilot_claude_sonnet_40 %} | Anthropic | GA | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gemini_25_pro %} | Google | GA | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gemini_flash %} | Google | GA | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gemini_25_pro %} | Google | GA | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gemini_flash %} | Google | GA | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_grok_code %} | xAI | {% data variables.release-phases.public_preview_caps %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
{% endrowheaders %}
@@ -60,20 +63,21 @@ The following table shows which models are available in each client.
{% rowheaders %}
| Model | {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_vscode %} | {% data variables.product.prodname_vs %} | Eclipse | Xcode | JetBrains IDEs |
-|----------------------------------------------------------------|------------|---------|----------------------------------------------|---------------------------------------------|---------------------------------------------|---------------------------------------------|
-| {% data variables.copilot.copilot_gpt_41 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gpt_5_mini %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} |
-| {% data variables.copilot.copilot_gpt_5 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} |
-| {% data variables.copilot.copilot_o3 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_o4_mini %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_opus_41 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} |
-| {% data variables.copilot.copilot_claude_opus %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_35 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_40 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gemini_25_pro %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gemini_flash %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+|----------------------------------------------------------------|----------------------------------------------------------|---------|----------------------------------------------|---------------------------------------------|---------------------------------------------|---------------------------------------------|
+| {% data variables.copilot.copilot_gpt_41 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gpt_5_mini %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} |
+| {% data variables.copilot.copilot_gpt_5 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} |
+| {% data variables.copilot.copilot_o3 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_o4_mini %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_opus_41 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} |
+| {% data variables.copilot.copilot_claude_opus %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_35 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_37 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_40 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gemini_25_pro %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gemini_flash %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_grok_code %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} |
{% endrowheaders %}
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/about-tasklists.md b/content/get-started/writing-on-github/working-with-advanced-formatting/about-tasklists.md
index 4a9650540ce8..75c8ef27ad3f 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/about-tasklists.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/about-tasklists.md
@@ -21,7 +21,7 @@ topics:
## About tasklists
> [!IMPORTANT]
-> Tasklists are {% data variables.release-phases.retired %}. You can read more about this on the [GitHub Blog](https://github.blog/changelog/2025-04-29-closing-down-code-scanning-alerts-tracked-in-tasklists/).
+> Tasklist blocks are {% data variables.release-phases.retired %}. You can read more about this on the [{% data variables.product.github %} Blog](https://github.blog/changelog/2025-02-18-github-issues-projects-february-18th-update/).
>
> {% ifversion sub-issues %} You can use sub-issues as the replacement for tasklist blocks. Sub-issues provide a dedicated section within each issue, making it easier to track related work without relying on Markdown. For more information about sub-issues, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues). {% endif %}
diff --git a/content/issues/guides.md b/content/issues/guides.md
index e3502dcd065e..cb4897b243d1 100644
--- a/content/issues/guides.md
+++ b/content/issues/guides.md
@@ -9,17 +9,25 @@ versions:
ghes: '*'
ghec: '*'
includeGuides:
- - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
- - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
- - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view
+ - /issues/tracking-your-work-with-issues/learning-about-issues/quickstart
- /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
- - /issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects
- - /issues/tracking-your-work-with-issues/configuring-issues/quickstart
+ - /issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project
+ - /issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects
- /issues/tracking-your-work-with-issues/using-issues/creating-an-issue
+ - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
+ - /issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization
+ - /issues/tracking-your-work-with-issues/using-issues/adding-sub-issues
- /issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests
- - /issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project
- /issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests
- - /issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards
- /issues/using-labels-and-milestones-to-track-work/managing-labels
- /issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests
+ - /issues/planning-and-tracking-with-projects/understanding-fields
+ - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project
+ - /issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts
+ - /issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization
+ - /issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations
+ - /issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects
+ - /issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project
+ - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
+
---
diff --git a/content/issues/index.md b/content/issues/index.md
index 00e246ab985d..71b2292fd663 100644
--- a/content/issues/index.md
+++ b/content/issues/index.md
@@ -3,22 +3,22 @@ title: "{% data variables.product.prodname_github_issues %} documentation"
shortTitle: "{% data variables.product.prodname_github_issues %}"
intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
introLinks:
- overview: /issues/tracking-your-work-with-issues/about-issues
- quickstart: /issues/tracking-your-work-with-issues/configuring-issues/quickstart
+ overview: /issues/tracking-your-work-with-issues/learning-about-issues/about-issues
+ quickstart: /issues/tracking-your-work-with-issues/learning-about-issues/quickstart
featuredLinks:
startHere:
- /issues/tracking-your-work-with-issues/using-issues/creating-an-issue
- /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
- /issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects
- /communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
- - /issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project
+ - /issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project
guideCards:
- /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view
- /issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue
- '{% ifversion ghes %}/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards{% endif %}'
- /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
popular:
- - /issues/tracking-your-work-with-issues/about-issues
+ - /issues/tracking-your-work-with-issues/learning-about-issues/about-issues
- /issues/planning-and-tracking-with-projects/learning-about-projects/about-projects
- /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
- /communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/finding-your-projects.md b/content/issues/planning-and-tracking-with-projects/finding-your-projects.md
similarity index 97%
rename from content/issues/planning-and-tracking-with-projects/learning-about-projects/finding-your-projects.md
rename to content/issues/planning-and-tracking-with-projects/finding-your-projects.md
index 7fb6a9588291..17a0a9b78074 100644
--- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/finding-your-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/finding-your-projects.md
@@ -1,6 +1,8 @@
---
title: 'Finding your {% data variables.projects.projects_v2 %}'
intro: 'Learn how to locate projects in your account, organizations, repositories, and teams.'
+redirect_from:
+ - /issues/planning-and-tracking-with-projects/learning-about-projects/finding-your-projects
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
diff --git a/content/issues/planning-and-tracking-with-projects/index.md b/content/issues/planning-and-tracking-with-projects/index.md
index 1d0a325ea07b..059237354668 100644
--- a/content/issues/planning-and-tracking-with-projects/index.md
+++ b/content/issues/planning-and-tracking-with-projects/index.md
@@ -16,6 +16,8 @@ children:
- /automating-your-project
- /viewing-insights-from-your-project
- /managing-your-project
+ - /finding-your-projects
+ - /sharing-project-updates
allowTitleToDifferFromFilename: true
redirect_from:
- /issues/trying-out-the-new-projects-experience
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
index e1999ef44fb7..344cf95eeb94 100644
--- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
@@ -15,7 +15,7 @@ topics:
## About {% data variables.product.prodname_projects_v2 %}
-A project is an adaptable spreadsheet, task-board, and road map that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, visualize work with configurable charts, and add custom fields to track metadata specific to your team. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
+A project is an adaptable table, board, and roadmap that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively at the user or organization level. You can create and customize multiple views by filtering, sorting, slicing, and grouping your issues and pull requests to manage your team backlogs and roadmaps, visualize work with configurable charts, add custom fields to track metadata specific to your team, create templates, share status updates, and automate your projects. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
To get started and create a project, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project). To learn more about the different layouts, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view).
@@ -25,6 +25,12 @@ Your projects are built from the issues and pull requests you add, creating dire
To learn more about managing items in your project, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project) and [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/editing-items-in-your-project).
+### Viewing your project from different perspectives
+
+Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer three different layout options.
+
+You can view your project as a high-density table layout, as a kanban board, or a timeline-style roadmap. These customized views help you manage your team backlog, perform iteration planning, plan your roadmap, plan for a feature release, or triage bugs, right next to the code. For more information about the different layout options, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view).
+
### Adding metadata to your items
You can use custom fields to add metadata to your issues, pull requests, and draft issues and build a richer view of item attributes. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields:
@@ -35,7 +41,7 @@ You can use custom fields to add metadata to your issues, pull requests, and dra
* A text field to add a quick note.
* An iteration field to plan work week-by-week, including support for breaks.
-You can use up to 50 fields in a project, including built-in metadata and custom fields. To learn more about the different fields you can add to a project, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields).
+You can use up to 50 fields in a project, including built-in metadata and custom fields. To learn more about the different fields you can add to a project, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields) and [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project).
### Automating your projects
@@ -43,8 +49,27 @@ There are a number of ways you can add automation to your project. Built-in work
You can also use the GraphQL API and {% data variables.product.prodname_actions %} to take even greater control of your project. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects) and [AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions).
-### Viewing your project from different perspectives
+### Viewing charts and insights
-Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer three different layout options.
+You can use insights for {% data variables.product.prodname_projects_v2 %} to view, create, and customize charts that use the items added to your project as their source data. You can apply filters to the default chart and also create your own charts. When you create a chart, you set the filters, chart type, the information displayed, and the chart is available to anyone that can view the project.
+
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects).
+
+### Creating project templates
+
+You can create project templates for your organization, or set a project as a template, to share a pre-configured project with other people in your organization which they can then use as the base for their projects. Project templates include the views, custom fields, draft issues and associated fields, configured workflows (except any auto-add workflows), and insights.
+
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization).
+
+### Sharing status updates
+
+You can keep your team up to date and share high-level overviews, which people can use to determine the status of your project. You can set a status, such as "On track" or "At risk", to allow people to quickly determine the current state of the project. You can also set start dates and target dates. Your status update can also contain a message that supports formatting with Markdown. Status updates are found on your project's side panel, below the description and README, and in the project's header and in lists when you're browsing projects.
+
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/sharing-project-updates).
+
+## Next steps
+
+Here are some helpful resources for taking your next steps with {% data variables.product.prodname_projects_v2 %}:
-You can view your project as a high-density table layout, as a kanban board, or a timeline-style roadmap. For more information about the different layout options, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view).
+* To learn about getting started using projects, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects).
+* To learn tips for managing your projects, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects).
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
index 208625fd7f22..574c9b22e3d5 100644
--- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
@@ -17,6 +17,10 @@ topics:
You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about {% data variables.product.prodname_projects_v2 %}, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
+## Communicate across your issues and pull requests
+
+Issues and pull requests include built-in features to let you easily communicate with your collaborators. Use @mentions to alert a person or entire team about a comment. Assign collaborators to issues to communicate responsibility. Link to related issues or pull requests to communicate how they are connected.
+
## Break down large issues into smaller issues
Breaking a large issue into smaller issues makes the work more manageable and enables team members to work in parallel. It also leads to smaller pull requests, which are easier to review.
@@ -25,11 +29,19 @@ To ensure efficient progress, clearly define which issues are blocked by, or blo
To track how smaller issues fit into the larger goal, use milestones or labels. For more information, see [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones) and [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels).
-## Communicate
+{% ifversion sub-issues %}
-Issues and pull requests include built-in features to let you easily communicate with your collaborators. Use @mentions to alert a person or entire team about a comment. Assign collaborators to issues to communicate responsibility. Link to related issues or pull requests to communicate how they are connected.
+{% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues).
+
+{% ifversion issue-types %}
-## Make use of the description, README, and status updates
+You can also use issue types to classify work in repositories across the organization alongside sub-issues. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization).
+
+{% endif %}
+
+{% endif %}
+
+## Make use of the description, README, and status updates to share information about a project
Use your project's description and README to share information about the project.
@@ -41,27 +53,52 @@ For example:
Project READMEs support Markdown which allows you to use images and advanced formatting such as links, lists, and headers. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project).
-You can also share high-level updates with other users of your project by posting status updates. Status updates allow you to mark the project with a status, such as "On track" or "At risk", set start and target dates, and share written updates with your team. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/sharing-project-updates).
+You can also share high-level updates with other users of your project by posting status updates. Status updates allow you to mark the project with a status, such as "On track" or "At risk", set start and target dates, and share written updates with your team. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/sharing-project-updates).
-## Use views
+## Create customized views of your project items
-Use project views to look at your project from different angles.
+Use project views to look at your project from different angles using the table, board, and roadmap layout. Views allow you to manage your team backlog, weekly iterations, team roadmaps, and plans for a feature release, just to name a few.
-For example:
+For example, you can customize views by:
-* Filter by status to view all un-started items
-* Group by a custom priority field to monitor the volume of high priority items
-* Sort by a custom date field to view the items with the earliest target ship date
+* Filtering by status to view all un-started items
+* Grouping by a custom priority field to monitor the volume of high priority items
+* Sorting by a custom date field to view the items with the earliest target ship date
+* Slicing by assignee to view team capacity
+* Showing a field sum for an estimate to highlight complexity for a group of items
+* Adding a column limit to a board column to maintain focus
-For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view).
+Here is an example table layout:
-## Have a single source of truth
+
-To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location.
+Here is an example board layout:
-{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project.
+
+
+Here is an example roadmap layout:
+
+
+
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project).
-## Use automation
+## Use different field types to add metadata to your project items
+
+Take advantage of the various field types to meet your needs and add metadata to your issues, pull requests, and draft issues for richer views. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields:
+
+* A date field to track target ship dates
+* A number field to track the complexity of a task
+* A single select field to track whether a task is Low, Medium, or High priority
+* A text field to add a quick note
+* An iteration field to plan work week-by-week, including support for breaks
+
+Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. See [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields).
+
+Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value.
+
+For more information about the different field types, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields).
+
+## Use automation to keep your projects up to date automatically
You can automate tasks to spend less time on busy work and more time on the project itself. The less you need to remember to do manually, the more likely your project will stay up to date.
@@ -76,12 +113,35 @@ Additionally, {% data variables.product.prodname_actions %} and the GraphQL API
* For more information about the API, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects).
* For more information about {% data variables.product.prodname_actions %}, see [AUTOTITLE](/actions).
-## Use different field types
+## Create charts and insights to visualize and share progress
-Take advantage of the various field types to meet your needs.
+You can use insights for {% data variables.product.prodname_projects_v2 %} to view, create, and customize charts that use the items added to your project as their source data. You can apply filters to the default chart and also create your own charts. When you create a chart, you set the filters, chart type, the information displayed, and the chart is available to anyone that can view the project.
-Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields).
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects).
-Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value.
+## Create project templates to standardize your workflows
-For more information about the different field types, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields).
+You can create project templates for your organization, or set a project as a template, to share a pre-configured project with other people in your organization which they can then use as the base for their projects. Project templates include the views, custom fields, draft issues and associated fields, configured workflows (except any auto-add workflows), and insights.
+
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization).
+
+## Link projects to teams and repositories
+
+You can add projects to your team to give the whole team collaborator access to their projects. When you add a project to a team, that project is listed on the team's projects page, making it easier for members to identify which projects a particular team uses.
+
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team).
+
+You can also add projects to a repository that is owned by the same user or organization that owns the project.
+
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository).
+
+## Have a single source of truth
+
+To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location.
+
+{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project.
+
+## Further reading
+
+* [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)
+* [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
index cd5f835d6c1c..d54538b4b542 100644
--- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
@@ -10,7 +10,5 @@ children:
- /about-projects
- /quickstart-for-projects
- /best-practices-for-projects
- - /finding-your-projects
- - /sharing-project-updates
allowTitleToDifferFromFilename: true
---
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
index b1047d882b29..bed015f3470a 100644
--- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
@@ -15,7 +15,7 @@ topics:
## Introduction
-This guide demonstrates how to use {% data variables.product.prodname_projects_v2 %} to plan and track work. In this guide, you will create a new project and add a custom field to track priorities for your tasks. You'll learn how to create saved views that help you communicate priorities and progress with your collaborators. You'll also set up built-in workflows to manage the items in your project.
+This guide demonstrates how to use {% data variables.product.prodname_projects_v2 %} to plan and track work. In this guide, you will create a new project, customize views, and add custom fields to manage a team backlog, iteration planning, and a team roadmap to communicate priorities and progress with your collaborators. You'll also set up built-in workflows to automatically manage the items in your project and charts to visualize items in your project.
## Prerequisites
@@ -39,13 +39,13 @@ First, create an organization project or a user project.
{% data reusables.projects.project-description %}
-## Adding issues to your project
+## Adding items to your project
-Next, add a few issues to your project.
+Next, add a few items to your project.
{% data reusables.projects.add-item-via-paste %}
-Repeat the above steps a few times to add multiple issues to your project.
+Repeat the above steps a few times to add multiple items to your project.
For more information and other ways to add issues to your project, or about other items you can add to your project, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project).
@@ -55,16 +55,22 @@ Next, add a draft issue to your project.
{% data reusables.projects.add-draft-issue %}
-## Adding an iteration field
+## Adding fields
-Next, create an iteration field so you can plan and track your work over repeating blocks of time. Iterations can be configured to suit how you and your team works, with customizable lengths and the ability to insert breaks.
+Next, create custom fields to manage the iteration, priority, and estimates for your project items.
+
+### Creating an iteration field
+
+Create an iteration field so you can plan and track your work over repeating blocks of time. Iterations can be configured to suit how you and your team works, with customizable lengths and the ability to insert breaks.
{% data reusables.projects.new-field %}
1. Select **Iteration**
1. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**.
1. Click **Save**.
-## Creating a field to track priority
+Specify an iteration for all items in your project.
+
+### Creating a priority field
Now, create a custom field named `Priority` and containing the values: `High`, `Medium`, or `Low`.
@@ -74,11 +80,37 @@ Now, create a custom field named `Priority` and containing the values: `High`, `
1. To add additional fields, for "Medium" and "Low", click **Add option**.
1. Click **Save**.
-Specify a priority for all issues in your project.
+Specify a priority for all items in your project.
-## Grouping issues by priority
+### Creating an estimate field
+
+Create a custom field named `Estimate` to track the complexity for each item.
+
+{% data reusables.projects.new-field %}
+1. Select **Number**
+1. Click **Save**.
+
+Specify an estimate for all items in your project.
+
+## Creating views
+
+Create views to visualize your items in a table, board, and roadmap.
+
+For more information on customizing views, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project).
+
+### Creating a team backlog
+
+You can use a table layout to visualize your team backlog as a spreadsheet, allowing you to view many fields and make edits.
+
+Select visible fields for your view to communicate the priority and progress of your team backlog.
+
+1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
+
+ 
+
+1. Under "Hidden fields", click {% ifversion issue-types %}**Type**, {% endif %}**Status**, {% ifversion sub-issues %}**Sub-issues progress**, {% endif %}**Assignees**, **Linked pull requests**, **Priority**, and **Estimate**.
Next, group all of the items in your project by priority to make it easier to focus on the high priority items.
@@ -86,37 +118,90 @@ Next, group all of the items in your project by priority to make it easier to fo
1. Click **{% octicon "rows" aria-hidden="true" aria-label="rows" %} Group**.
1. Click **Priority**.
-Now, move issues between groups to change their priority.
+Now, move items between groups to change their priority.
-1. Choose an issue.
-1. Drag and drop the issue into a different priority group. When you do this, the priority of the issue will change to be the priority of its new group.
+1. Choose an item.
+1. Drag and drop the item into a different priority group. When you do this, the priority of the item will change to be the priority of its new group.
-## Saving the priority view
+You can also show the sum of the `Estimate` field for each priority group.
+
+{% data reusables.projects.open-view-menu %}
+1. Click **{% octicon "number" aria-hidden="true" aria-label="number" %} Field sum**.
+1. Select **Estimate**.
-When you grouped your issues by priority in the previous step, your project displayed an indicator to show that the view was modified. Save these changes so that your collaborators will also see the tasks grouped by priority.
+When you grouped your items by priority and added a field sum in the previous steps, your project displayed an indicator to show that the view was modified. Save these changes so that your collaborators will also see the tasks grouped by priority.
{% data reusables.projects.save-view %}
-You can share the URL with your team to keep everyone aligned on the project priorities.
+You can share the URL with your team to keep everyone aligned on the project priorities. When a view is saved, anyone who opens the project will see the saved view. Here, you grouped by priority, but you can also add other modifiers such as sort, filter, or layout.
+
+Finally, to indicate the purpose of the view, give it a descriptive name.
+
+{% data reusables.projects.open-view-menu %}
+1. Click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Rename view**.
+1. Type the new name for your view.
+1. To save changes, press Return.
-When a view is saved, anyone who opens the project will see the saved view. Here, you grouped by priority, but you can also add other modifiers such as sort, filter, or layout. Next, you will create a new view with the layout modified.
+Next, you will create new views with different layouts.
-## Adding a board layout
+For more information on customizing tables, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout).
-To view the progress of your project's issues, you can switch to board layout.
+### Creating a weekly iteration board view
-The board layout is based on the status field, so specify a status for each issue in your project.
+To view the progress of your project's items in a kanban board, you can use the board layout. The board layout is based on the status field by default, so specify a status for each item in your project.
-Then, create a new view.
+First, create a new view.
{% data reusables.projects.new-view %}
-Next, switch to board layout.
+Next, switch to the board layout.
{% data reusables.projects.open-view-menu %}
1. Under "Layout", click **Board**.
-When you changed the layout, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future.
+To indicate the purpose of the view, give it a descriptive name.
+
+{% data reusables.projects.open-view-menu %}
+1. Click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Rename view**.
+1. Type the new name for your view.
+1. To save changes, press Return.
+
+Add a filter for `iteration:@current` to only includes items from the current iteration.
+
+You can also show the sum of the `Estimate` field for each status column.
+
+{% data reusables.projects.open-view-menu %}
+1. Click **{% octicon "number" aria-hidden="true" aria-label="number" %} Field sum**.
+1. Select **Estimate**.
+
+When you added a filter and added a field sum in the previous steps, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future.
+
+{% data reusables.projects.save-view %}
+
+For more information on customizing boards, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout).
+
+### Creating a team roadmap
+
+To view your project items on a timeline, you can use the roadmap layout. Roadmaps use custom date and iteration fields to position your issues, pull requests, and draft items on a timeline, allowing you to track work over time and watch progress.
+
+First, create a new view.
+
+{% data reusables.projects.new-view %}
+
+Next, switch to the roadmap layout.
+
+{% data reusables.projects.open-view-menu %}
+1. Under "Layout", click **Roadmap**.
+
+You can add vertical markers on a roadmap to show the milestones associated with items in your project.
+
+1. In the top right of your roadmap, click **{% octicon "location" aria-hidden="true" aria-label="location" %} Markers**.
+
+ 
+
+1. In the menu, select which markers you want to display on your roadmap.
+
+When you added markers, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future.
{% data reusables.projects.save-view %}
@@ -127,7 +212,9 @@ To indicate the purpose of the view, give it a descriptive name.
1. Type the new name for your view.
1. To save changes, press Return.
-## Configure built-in automation
+For more information on customizing roadmaps, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout).
+
+## Configuring built-in automation
Next, configure the auto-add workflow to automatically add issues opened in a repository with a specific label to your project.
@@ -138,7 +225,7 @@ Next, configure the auto-add workflow to automatically add issues opened in a re
1. Under "Filters", select the repository you want to add items from.
-1. Next to the repository selection, type the filter criteria you want items to match before they are automatically added to your project. For example, to catch all issues and PRs opened with the label "bug", use `is:issue,pr label:bug`.
+1. Next to the repository selection, type the filter criteria you want items to match before they are automatically added to your project. For example, to catch all issues and pull requests opened with the label "question", use `is:issue,pr label:question`.
1. To enable the new workflow, click **Save and turn on workflow**.
Finally, add a built in workflow to set the status to **Todo** when an item is added to your project.
@@ -151,7 +238,22 @@ Finally, add a built in workflow to set the status to **Todo** when an item is a
1. Next to **Set**, select **Status:Todo**.
1. Click the **Disabled** toggle to enable the workflow.
+For more information on automating your project and other default workflows you can configure to keep your project items up to date, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project).
+
+## Viewing charts and insights
+
+You can use insights for {% data variables.product.prodname_projects_v2 %} to view, create, and customize charts that use the items added to your project as their source data. You can apply filters to the default chart and also create your own charts by choosing the grouping, layout, X-axis, and Y-axis configuration.
+
+{% data reusables.projects.access-insights %}
+1. In the menu on the left, click **New chart**.
+1. Optionally, to change the name of the new chart, click {% octicon "triangle-down" aria-label="The triangle icon" %}, type a new name, and press Return.
+1. Above the chart, type filters to change the data used to build the chart. See [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects).
+1. To the right of the filter text box, click **Save changes**.
+
+For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects).
+
## Further reading
-* [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)
-* [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view)
+* [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects)
+* [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project)
+* [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields)
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/sharing-project-updates.md b/content/issues/planning-and-tracking-with-projects/sharing-project-updates.md
similarity index 95%
rename from content/issues/planning-and-tracking-with-projects/learning-about-projects/sharing-project-updates.md
rename to content/issues/planning-and-tracking-with-projects/sharing-project-updates.md
index d7859bf58ab2..a5f5a8ed2a6e 100644
--- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/sharing-project-updates.md
+++ b/content/issues/planning-and-tracking-with-projects/sharing-project-updates.md
@@ -1,6 +1,8 @@
---
title: 'Sharing {% data variables.projects.project_v2 %} updates'
intro: 'You can post updates to your {% data variables.projects.projects_v2 %} that share the current status, start date, and target date of the {% data variables.projects.project_v2 %} itself.'
+redirect_from:
+ - /issues/planning-and-tracking-with-projects/learning-about-projects/sharing-project-updates
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-fields/about-parent-issue-and-sub-issue-progress-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-parent-issue-and-sub-issue-progress-fields.md
index 24b61d153ee2..40f8544d9e6f 100644
--- a/content/issues/planning-and-tracking-with-projects/understanding-fields/about-parent-issue-and-sub-issue-progress-fields.md
+++ b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-parent-issue-and-sub-issue-progress-fields.md
@@ -31,7 +31,7 @@ You can enable the "Parent issue" field to see which parent issues the issues in
1. Under "Hidden fields", click **Parent issue**.
-## Enabling the Sub-issue progress
+## Enabling the Sub-issue progress field
You can enable the "Sub-issue progress" field to see how many sub-issues have been completed.
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-fields/about-pull-request-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-pull-request-fields.md
new file mode 100644
index 000000000000..df0a34e81625
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-pull-request-fields.md
@@ -0,0 +1,33 @@
+---
+title: About pull request fields
+shortTitle: About pull request fields
+intro: 'You can show a linked pull request and the pull request reviewers in your projects.'
+versions:
+ fpt: '*'
+ ghec: '*'
+type: tutorial
+topics:
+ - Projects
+---
+
+You can enable the "Linked pull requests" and "Reviewers" fields on your projects to see information about a pull request, making a project the way to plan and track your issues, pull request, and code.
+
+## Enabling the Linked pull requests field
+
+You can enable the "Linked pull requests" field to see the pull request linked to an issue, allowing you to see the state of the pull request.
+
+1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
+
+ 
+
+1. Under "Hidden fields", click **Linked pull requests**.
+
+## Enabling the Reviewers field
+
+You can enable the "Reviewers" field to see the reviewers on the pull request.
+
+1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
+
+ 
+
+1. Under "Hidden fields", click **Reviewers**.
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-fields/about-the-issue-type-field.md b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-the-issue-type-field.md
new file mode 100644
index 000000000000..a5bb89f123a3
--- /dev/null
+++ b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-the-issue-type-field.md
@@ -0,0 +1,24 @@
+---
+title: About the issue type field
+shortTitle: About the issue type field
+intro: 'You can show the type of the issue in your projects.'
+versions:
+ feature: issue-types
+type: tutorial
+topics:
+ - Projects
+---
+
+If your organization uses issue types, you can enable the "Type" field on your projects to see the issue type and how the issue is classified in your organization, such as a bug, task, or feature.
+
+For more about issue types, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization).
+
+## Enabling the Type field
+
+You can enable the "Type" field to see the type of the issue.
+
+1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
+
+ 
+
+1. Under "Hidden fields", click **Type**.
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-fields/index.md b/content/issues/planning-and-tracking-with-projects/understanding-fields/index.md
index d2da9f2f4e79..1a7ee8729e85 100644
--- a/content/issues/planning-and-tracking-with-projects/understanding-fields/index.md
+++ b/content/issues/planning-and-tracking-with-projects/understanding-fields/index.md
@@ -13,6 +13,8 @@ children:
- /about-single-select-fields
- /about-iteration-fields
- /about-parent-issue-and-sub-issue-progress-fields
+ - /about-pull-request-fields
+ - /about-the-issue-type-field
- /renaming-custom-fields
- /deleting-custom-fields
allowTitleToDifferFromFilename: true
@@ -20,4 +22,3 @@ redirect_from:
- /issues/planning-and-tracking-with-projects/understanding-field-types
- /issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields
---
-
diff --git a/content/issues/tracking-your-work-with-issues/index.md b/content/issues/tracking-your-work-with-issues/index.md
index 9029bc314541..288587b9617f 100644
--- a/content/issues/tracking-your-work-with-issues/index.md
+++ b/content/issues/tracking-your-work-with-issues/index.md
@@ -9,11 +9,11 @@ versions:
topics:
- Issues
children:
- - /about-issues
- - /configuring-issues
+ - /learning-about-issues
- /using-issues
- /administering-issues
redirect_from:
- /issues/tracking-your-work-with-issues/creating-issues
- /issues/tracking-your-work-with-issues/managing-issues
+ - /issues/tracking-your-work-with-issues/configuring-issues
---
diff --git a/content/issues/tracking-your-work-with-issues/about-issues.md b/content/issues/tracking-your-work-with-issues/learning-about-issues/about-issues.md
similarity index 72%
rename from content/issues/tracking-your-work-with-issues/about-issues.md
rename to content/issues/tracking-your-work-with-issues/learning-about-issues/about-issues.md
index 449f90732fe2..f723601f4a29 100644
--- a/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/content/issues/tracking-your-work-with-issues/learning-about-issues/about-issues.md
@@ -7,6 +7,7 @@ redirect_from:
- /articles/about-issues
- /github/managing-your-work-on-github/about-issues
- /issues/tracking-your-work-with-issues/creating-issues/about-issues
+ - /issues/tracking-your-work-with-issues/about-issues
versions:
fpt: '*'
ghes: '*'
@@ -17,7 +18,7 @@ topics:
- Project management
---
-You can create issues in your repository to plan, discuss, and track work. Issues are quick to create, flexible, and can be used in many ways. Issues can track bug reports, new features and ideas, and anything else you need to write down or discuss with your team. {% ifversion sub-issues %}You can also break your work down further by adding sub-issues and easily browse the full hierarchy of work to be done.{% endif %}
+You can create issues in your repository to plan, discuss, and track work. Issues are quick to create, flexible, and can be used in many ways. Issues can track bug reports, new features and ideas, and anything else you need to write down or discuss with your team, and you can use {% data variables.projects.projects_v2 %} to plan and track the work for your team. {% ifversion sub-issues %}You can also break your work down further by adding sub-issues and easily browse the full hierarchy of work to be done.{% endif %}
Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow. For example, you can create an issue from a repository,{% ifversion sub-issues %} while adding sub-issues,{% endif %} convert a comment in an issue or pull request, create an issue from a specific line of code, or via a URL query. You can also create an issue from your platform of choice: through the web UI, {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL and REST APIs, or {% data variables.product.prodname_mobile %}. See [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue).
@@ -43,7 +44,9 @@ You can define blocking relationships between issues using issue dependencies. I
Issues integrate with your work all across {% data variables.product.github %}. Mentioning an issue in another issue or pull request will create references between them and using keywords, like `fixes:`, in your pull requests will automatically close the associated issues. See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue).
-{% data variables.projects.projects_v2_caps %} is strongly integrated with issues. All your issue metadata is available in your projects, allowing you to create views and filters to represent your work. See [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
+## Using {% data variables.projects.projects_v2_caps %} to plan and track your work
+
+{% data variables.projects.projects_v2_caps %} is strongly integrated with issues to plan and track the work for your team. All your issue metadata is available in your projects, allowing you to create views and filters to represent your work. See [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
## Staying up to date
@@ -63,8 +66,30 @@ You can @mention collaborators who have access to your repository in an issue to
{% ifversion fpt or ghec %} See [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) and [AUTOTITLE](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users).
{% endif %}
+## Metadata on issues
+
+You can add metadata to your issues, including {% ifversion issue-types %}issue types, {% endif %}labels and milestones to organize your issues.
+
+See {% ifversion issue-types %}[AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization), {% endif %}[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels) and [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones).
+
+{% ifversion sub-issues %}
+
+## About sub-issues
+
+{% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues).
+
+{% endif %}
+
## Comparing issues and discussions
Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see [AUTOTITLE](/get-started/using-github/communicating-on-github).
When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion.
+
+## Next steps
+
+Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}:
+
+* To learn about getting started using issues, see [AUTOTITLE](/issues/tracking-your-work-with-issues/learning-about-issues/quickstart).
+* To learn about the essentials for using GitHub's planning and tracking tools, see [AUTOTITLE](/issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project).
+* To learn more about how projects can help you with planning and tracking, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects).
diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/index.md b/content/issues/tracking-your-work-with-issues/learning-about-issues/index.md
similarity index 52%
rename from content/issues/tracking-your-work-with-issues/configuring-issues/index.md
rename to content/issues/tracking-your-work-with-issues/learning-about-issues/index.md
index 9eb6f25af42a..9f4c05d71316 100644
--- a/content/issues/tracking-your-work-with-issues/configuring-issues/index.md
+++ b/content/issues/tracking-your-work-with-issues/learning-about-issues/index.md
@@ -1,6 +1,6 @@
---
-title: Configuring issues
-intro: 'Learn how to configure your repository to start using issues.'
+title: Learning about issues
+intro: 'Learn about issues and how to make the best of this powerful tool.'
versions:
fpt: '*'
ghes: '*'
@@ -8,7 +8,7 @@ versions:
topics:
- Issues
children:
+ - /about-issues
- /quickstart
- /planning-and-tracking-work-for-your-team-or-project
- - /managing-issue-types-in-an-organization
---
diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md b/content/issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project.md
similarity index 87%
rename from content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md
rename to content/issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project.md
index 4bf98f7748ff..5f85e42c418f 100644
--- a/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md
+++ b/content/issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project.md
@@ -11,12 +11,13 @@ topics:
- Projects
redirect_from:
- /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
+ - /issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project
---
## Introduction
You can use {% data variables.product.prodname_dotcom %} repositories, issues, projects, and other tools to plan and track your work, whether working on an individual project or cross-functional team.
-In this guide, you will learn how to create and set up a repository for collaborating with a group of people, create issue templates and forms, open issues and use task lists to break down work, and establish a {% data variables.projects.project_v2 %} for organizing and tracking issues.
+In this guide, you will learn how to create and set up a repository for collaborating with a group of people, create issue templates and forms, open issues and break down work, and establish a {% data variables.projects.project_v2 %} for organizing and tracking issues.
## Creating a repository
@@ -66,7 +67,7 @@ Now that we created the bug report issue template, you are able to select it whe
-## Opening issues and using task lists to track work
+## Opening issues and breaking down work
You can organize and track your work by creating issues. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue).
@@ -76,6 +77,22 @@ Here is an example of an issue created for a large initiative, front-end work, i
+{% ifversion sub-issues %}
+
+### Sub-issues example
+
+{% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues).
+
+{% ifversion issue-types %}
+
+You can use issue types to classify work in repositories across the organization, such as tasks, bugs, and features. See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization).
+
+{% endif %}
+
+ 
+
+{% endif %}
+
### Task list example
You can use task lists to break larger issues down into smaller tasks and to track issues as part of a larger goal. {% ifversion fpt or ghec %} Task lists have additional functionality when added to the body of an issue. You can see the number of tasks completed out of the total at the top of the issue, and if someone closes an issue linked in the task list, the checkbox will automatically be marked as complete.{% endif %} For more information, see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists).
@@ -84,13 +101,17 @@ Below we have added a task list to our Project Octocat issue, breaking it down i
-{% ifversion sub-issues %}
+## Using labels to highlight project goals and status
-### Breaking down your work with sub-issues
+You can create labels for a repository to categorize issues, pull requests, and discussions. {% data variables.product.prodname_dotcom %} also provides default labels for every new repository that you can edit or delete. Labels are useful for keeping track of project goals, bugs, types of work, and the status of an issue. See [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label).
-{% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues).
+Once you have created a label in a repository, you can apply it on any issue, pull request, or discussion in the repository. You can then filter issues and pull requests by label to find all associated work. For example, find all the front end bugs in your project by filtering for issues with the `front-end` and `bug` labels. See [AUTOTITLE](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests).
-{% endif %}
+### Label example
+
+Below is an example of a `front-end` label that we created and added to the issue.
+
+
### Showing which issues are blocked by, or blocking, other work
@@ -188,10 +209,12 @@ Below is a {% data variables.projects.projects_v1_board %} for our example Proje
You have now learned about the tools {% data variables.product.prodname_dotcom %} offers for planning and tracking your work, and made a start in setting up your cross-functional team or project repository! Here are some helpful resources for further customizing your repository and organizing your work.
* [AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories) for learning more about creating repositories
+* [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects) for learning more about projects
+* [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view) for learning how to customize views for projects
* [AUTOTITLE](/issues/tracking-your-work-with-issues) for learning more about different ways to create and manage issues
-* [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates) for learning more about issue templates
-* [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels) for learning how to create, edit and delete labels
+* [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates) for learning more about issue templates{% ifversion issue-types %}
+* [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization) for managing issue types{% endif %}
+* [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels) for learning how to create, edit and delete labels{% ifversion sub-issues %}
+* [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) for learning about adding sub-issues{% endif %}
* [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists) for learning more about task lists
-* [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) for learning more about projects
-* [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view) for learning how to customize views for projects
{% ifversion projects-v1 %}- [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards) for learning how to manage {% data variables.projects.projects_v1_boards %}{% endif %}
diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/quickstart.md b/content/issues/tracking-your-work-with-issues/learning-about-issues/quickstart.md
similarity index 72%
rename from content/issues/tracking-your-work-with-issues/configuring-issues/quickstart.md
rename to content/issues/tracking-your-work-with-issues/learning-about-issues/quickstart.md
index 731b95c785e5..9168a63c095b 100644
--- a/content/issues/tracking-your-work-with-issues/configuring-issues/quickstart.md
+++ b/content/issues/tracking-your-work-with-issues/learning-about-issues/quickstart.md
@@ -12,11 +12,12 @@ topics:
- Project management
redirect_from:
- /issues/tracking-your-work-with-issues/quickstart
+ - /issues/tracking-your-work-with-issues/configuring-issues/quickstart
---
## Introduction
-This guide demonstrates how to use {% data variables.product.prodname_github_issues %} to plan and track a piece of work. In this guide, you will create a new issue and add a task list to track sub-tasks. You'll also learn how to add labels, milestones, assignees, and projects to communicate metadata about your issue.
+This guide demonstrates how to use {% data variables.product.prodname_github_issues %} to plan and track a piece of work. In this guide, you will create a new issue{% ifversion sub-issues %} and break it down into sub-issues{% endif %}. You'll also learn how to add labels{% ifversion issue-types %}, issue types{% endif %}, milestones, assignees, and projects to communicate metadata about your issue.
## Prerequisites
@@ -41,31 +42,37 @@ You can use markdown to add formatting, links, emojis, and more. For more inform
+{% ifversion sub-issues %}
+
## Adding a task list
-It can be helpful to break large issues into smaller tasks, or to track multiple related issues in a single larger issue. Add a task list to your issue by prefacing list items with `[ ]`. Reference existing issues by issue number or URL. You can use plain text to track tasks that don't have a corresponding issue and convert them to issues later. For more information, see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists).
+You can also use plain text to track tasks that don't have a corresponding issue and convert them to issues later. For more information, see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists).
+## Assigning the issue
+
+To communicate responsibility, you can assign the issue to a member of your organization. See [AUTOTITLE](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users).
+
+
+
## Adding labels
-Add a label to categorize your issue. For example, you might use a `bug` label and a `good first issue` label to indicate that an issue is a bug that a first-time contributor could pick up. Users can filter issues by label to find all issues that have a specific label.
+Add a label to categorize your issue. For example, you might use a `question` label and a `good first issue` label to indicate that an issue is a question that a first-time contributor could pick up. Users can filter issues by label to find all issues that have a specific label.
You can use the default labels, or you can create a new label. For more information, see [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels).
-## Adding milestones
-
-You can add a milestone to track the issue as part of a date based target. A milestone will show the progress of the issues as the target date approaches. For more information, see [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones).
+{% ifversion issue-types %}
-
+## Adding issue types
-## Assigning the issue
+You can add an issue type to classify work across the organization. See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization).
-To communicate responsibility, you can assign the issue to a member of your organization. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users).
+
-
+{% endif %}
## Adding the issue to a project
@@ -73,10 +80,24 @@ You can add the issue to an existing project and populate metadata for the proje
+## Adding milestones
+
+You can add a milestone to track the issue as part of a date based target. A milestone shows the progress of the issues as the target date approaches. See [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones).
+
+
+
## Submitting your issue
Click **Submit new issue** to create your issue. You can edit any of the above fields after creating the issue. Your issue has a unique URL that you can share with team members, or reference in other issues or pull requests.
+## Adding sub-issues
+
+{% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues).
+
+ 
+
+{% endif %}
+
## Communicating
After your issue is created, continue the conversation by adding comments to the issue. You can @mention collaborators or teams to draw their attention to a comment. To link related issues in the same repository, you can type `#` followed by part of the issue title and then clicking the issue that you want to link. For more information, see [AUTOTITLE](/get-started/writing-on-github).
@@ -101,5 +122,6 @@ To break your issue down into more manageable tasks, you can add multiple levels
Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}:
* To learn more about issues, see [AUTOTITLE](/issues/tracking-your-work-with-issues/about-issues).
-* To learn more about how projects can help you with planning and tracking, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
+* To learn about the essentials for using {% data variables.product.github %}'s planning and tracking tools, see [AUTOTITLE](/issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project).
+* To learn more about how projects can help you with planning and tracking, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects).
* To learn more about using issue templates{% ifversion fpt or ghec %} and issue forms{% endif %} to encourage contributors to provide specific information, see [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests).
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/index.md b/content/issues/tracking-your-work-with-issues/using-issues/index.md
index ec7f7593ac7a..ce2f0e53ff41 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/index.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/index.md
@@ -19,4 +19,5 @@ children:
- /creating-a-branch-for-an-issue
- /linking-a-pull-request-to-an-issue
- /about-slash-commands
+ - /managing-issue-types-in-an-organization
---
diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md b/content/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization.md
similarity index 95%
rename from content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md
rename to content/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization.md
index 73b07b7be042..e4394776b8f7 100644
--- a/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization.md
@@ -1,8 +1,10 @@
---
title: Managing issue types in an organization
intro: 'Learn about issue types and how to manage them in your organization.'
+redirect_from:
+ - /issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization
versions:
- feature: 'issue-types'
+ feature: issue-types
type: overview
topics:
- Project management
diff --git a/content/site-policy/privacy-policies/github-subprocessors.md b/content/site-policy/privacy-policies/github-subprocessors.md
index 0883ecccbd99..05be3f7e841a 100644
--- a/content/site-policy/privacy-policies/github-subprocessors.md
+++ b/content/site-policy/privacy-policies/github-subprocessors.md
@@ -25,36 +25,37 @@ If you have questions about this list, please contact us at
## Third Party Subprocessors
-| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location |
-| --------------------------- | ------------------------------------------------------------------------------ | ----------------------- | ------------------ |
-| Amazon Web Services Inc (AWS) | Cloud Hosted Infrastructure, Data Hosting, AI Inference and AI Services | United States | United States |
-| Anthropic PBC | AI Inference and AI Services | United States | United States |
-| Cloudflare | Content delivery service | United States | United States |
-| CoreWeave, Inc. | Cloud Hosted Infrastructure | United States | United States |
-| Fastly | Content delivery service | United States | United States |
-| Google Cloud Platform (GCP) | Cloud Hosted Infrastructure, AI Inference and AI Services | United States, Belgium, Singapore | United States |
-| Hewlett-Packard Limited | Cloud Hosted Infrastructure | United States | United States |
-| LambdaTest | Cloud Hosted Infrastructure | United States | United States |
-| Microsoft (Azure) | Cloud Hosted Infrastructure, Data Hosting, AI Inference and AI Services | United States | United States |
-| Microsoft (Azure) | Cognitive Services and customer support ticketing analysis | United States | United States |
-| Microsoft | Technical Services | Australia, Brazil, Canada, France, Japan, Norway, Spain, Sweden, Switzerland, United Kingdom, United States | United States|
-| Moveworks | Customer support ticketing analysis | United States | United States |
-| NexMo Inc (aka Vonage) | SMS notification provider for 2 Factor Authentication | United States | United States |
-| Obsidian Security | Security management | United States | United States |
-| OpenAI | AI Inference and AI Services | United States | United States |
-| Oracle America, Inc. | Cloud Hosted Infrastructure | United States | United States |
-| Pusher | Building and managing real-time infrastructure for web and mobile applications | United States | United States |
-| Twilio (SendGrid) | SMS notification provider for 2 Factor Authentication | United States | United States |
-| Zendesk | Customer support ticketing system | United States | United States |
+| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location |
+|-------------------------------|--------------------------------------------------------------------------------| ----------------------- | ------------------ |
+| Amazon Web Services Inc (AWS) | Cloud Hosted Infrastructure, Data Hosting, AI Inference and AI Services | United States | United States |
+| Anthropic PBC | AI Inference and AI Services | United States | United States |
+| Cloudflare | Content delivery service | United States | United States |
+| CoreWeave, Inc. | Cloud Hosted Infrastructure | United States | United States |
+| Fastly | Content delivery service | United States | United States |
+| Google Cloud Platform (GCP) | Cloud Hosted Infrastructure, AI Inference and AI Services | United States, Belgium, Singapore | United States |
+| Hewlett-Packard Limited | Cloud Hosted Infrastructure | United States | United States |
+| LambdaTest | Cloud Hosted Infrastructure | United States | United States |
+| Microsoft (Azure) | Cloud Hosted Infrastructure, Data Hosting, AI Inference and AI Services | United States | United States |
+| Microsoft (Azure) | Cognitive Services and customer support ticketing analysis | United States | United States |
+| Microsoft | Technical Services | Australia, Brazil, Canada, France, Japan, Norway, Spain, Sweden, Switzerland, United Kingdom, United States | United States|
+| Moveworks | Customer support ticketing analysis | United States | United States |
+| NexMo Inc (aka Vonage) | SMS notification provider for 2 Factor Authentication | United States | United States |
+| Obsidian Security | Security management | United States | United States |
+| OpenAI | AI Inference and AI Services | United States | United States |
+| Oracle America, Inc. | Cloud Hosted Infrastructure | United States | United States |
+| Pusher | Building and managing real-time infrastructure for web and mobile applications | United States | United States |
+| Twilio (SendGrid) | SMS notification provider for 2 Factor Authentication | United States | United States |
+| xAI | AI Inference and AI Services | United States | United States |
+| Zendesk | Customer support ticketing system | United States | United States |
## GitHub Subsidiaries
-| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location |
-| --------------------------- | ------------------------------------------------------------------------------ | ----------------------- | ------------------ |
-| GitHub Australia Pty Ltd | GitHub Subsidiary | Australia | Australia |
-| GitHub BV | GitHub Subsidiary | Netherlands | Netherlands |
-| GitHub Canada ULC | GitHub Subsidiary | Canada | Canada |
-| GitHub Germany GmbH | GitHub Subsidiary | Germany | Germany |
-| GitHub India Pty Ltd | GitHub Subsidiary | India | India |
-| npm Inc | GitHub Subsidiary | United States | United States |
-| Semmle Inc | GitHub Subsidiary | United States | United States |
+| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location |
+|--------------------------|--------------------------------|--------------------------------|---------------------|
+| GitHub Australia Pty Ltd | GitHub Subsidiary | Australia | Australia |
+| GitHub BV | GitHub Subsidiary | Netherlands | Netherlands |
+| GitHub Canada ULC | GitHub Subsidiary | Canada | Canada |
+| GitHub Germany GmbH | GitHub Subsidiary | Germany | Germany |
+| GitHub India Pty Ltd | GitHub Subsidiary | India | India |
+| npm Inc | GitHub Subsidiary | United States | United States |
+| Semmle Inc | GitHub Subsidiary | United States | United States |
diff --git a/data/reusables/copilot/available-models-per-plan.md b/data/reusables/copilot/available-models-per-plan.md
index 5b453263ceea..c6cd9820fc5a 100644
--- a/data/reusables/copilot/available-models-per-plan.md
+++ b/data/reusables/copilot/available-models-per-plan.md
@@ -1,19 +1,20 @@
{% rowheaders %}
-| Available models in chat | {% data variables.copilot.copilot_free_short %} | {% data variables.copilot.copilot_pro_short %} | {% data variables.copilot.copilot_pro_plus_short %} | {% data variables.copilot.copilot_business_short %} | {% data variables.copilot.copilot_enterprise_short %} |
-|----------------------------------------------------------------|-------------------------------------------------|--------------------------------------------------|------------------------------------------------------|-------------------------------------------------------|----------------------------------------------------------|
-| {% data variables.copilot.copilot_gpt_41 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gpt_5_mini %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gpt_5 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_o3 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_o4_mini %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_opus_41 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_opus %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_35 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_claude_sonnet_40 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gemini_25_pro %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.copilot.copilot_gemini_flash %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| Available models in chat | {% data variables.copilot.copilot_free_short %} | {% data variables.copilot.copilot_pro_short %} | {% data variables.copilot.copilot_pro_plus_short %} | {% data variables.copilot.copilot_business_short %} | {% data variables.copilot.copilot_enterprise_short %} |
+|--------------------------------------------------------------|-------------------------------------------------|--------------------------------------------------|------------------------------------------------------|-------------------------------------------------------|----------------------------------------------------------|
+| {% data variables.copilot.copilot_gpt_41 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gpt_5_mini %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gpt_5 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_o3 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_o4_mini %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_opus_41 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_opus %} | {% octicon "x" aria-label="Not included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_35 %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_37 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_claude_sonnet_40 %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gemini_25_pro %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_gemini_flash %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.copilot.copilot_grok_code %} | {% octicon "x" aria-label="Not included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
{% endrowheaders %}
diff --git a/data/reusables/copilot/grok-promo-period.md b/data/reusables/copilot/grok-promo-period.md
new file mode 100644
index 000000000000..d7895c00583f
--- /dev/null
+++ b/data/reusables/copilot/grok-promo-period.md
@@ -0,0 +1 @@
+> [!Important] Complimentary access for {% data variables.copilot.copilot_grok_code %} is available until 1 p.m. PDT on Tuesday, September 2, 2025. [Regular pricing](/copilot/reference/ai-models/supported-models#model-multipliers) applies after that point.
diff --git a/data/reusables/copilot/model-multipliers.md b/data/reusables/copilot/model-multipliers.md
index 301d550eb9a9..8103622e4662 100644
--- a/data/reusables/copilot/model-multipliers.md
+++ b/data/reusables/copilot/model-multipliers.md
@@ -6,6 +6,8 @@
| {% data variables.copilot.copilot_gpt_5_mini %} | 0 | 1 |
| {% data variables.copilot.copilot_gpt_5 %} | 1 | Not applicable |
| {% data variables.copilot.copilot_gpt_4o %} | 0 | 1 |
+| {% data variables.copilot.copilot_o3 %} | 1 | Not applicable |
+| {% data variables.copilot.copilot_o4_mini %} | 0.33 | Not applicable |
| {% data variables.copilot.copilot_claude_sonnet_35 %} | 1 | 1 |
| {% data variables.copilot.copilot_claude_sonnet_37 %} | 1 | Not applicable |
| {% data variables.copilot.copilot_claude_sonnet_37 %} Thinking | 1.25 | Not applicable |
@@ -14,7 +16,6 @@
| {% data variables.copilot.copilot_claude_opus %} | 10 | Not applicable |
| {% data variables.copilot.copilot_gemini_flash %} | 0.25 | 1 |
| {% data variables.copilot.copilot_gemini_25_pro %} | 1 | Not applicable |
-| {% data variables.copilot.copilot_o3 %} | 1 | Not applicable |
-| {% data variables.copilot.copilot_o4_mini %} | 0.33 | Not applicable |
+| {% data variables.copilot.copilot_grok_code %} | 0.25 | Not applicable |
{% endrowheaders %}
diff --git a/data/reusables/issues/about-sub-issues.md b/data/reusables/issues/about-sub-issues.md
index 413a0486938e..ed04c2653c7c 100644
--- a/data/reusables/issues/about-sub-issues.md
+++ b/data/reusables/issues/about-sub-issues.md
@@ -1 +1 @@
-You can add sub-issues to an issue to quickly break down larger pieces of work into tasks. Sub-issues add support for hierarchies of issues on {% data variables.product.github %} by creating relationships between your issues. You can create multiple levels of sub-issues that accurately represent your project by breaking down tasks into exactly the amount of detail that you and your team require.
+You can add sub-issues to an issue to quickly break down larger pieces of work into smaller issues. Sub-issues add support for hierarchies of issues on {% data variables.product.github %} by creating relationships between your issues. You can create multiple levels of sub-issues that accurately represent your project by breaking down tasks into exactly the amount of detail that you and your team require.
diff --git a/data/variables/copilot.yml b/data/variables/copilot.yml
index 17368af3c861..2e1308d410d3 100644
--- a/data/variables/copilot.yml
+++ b/data/variables/copilot.yml
@@ -116,6 +116,8 @@ copilot_gpt_5_mini: 'GPT-5 mini'
# OpenAI 'o' series:
copilot_o3: 'o3'
copilot_o4_mini: 'o4-mini'
+## xAI:
+copilot_grok_code: 'Grok Code Fast 1'
## Next edit suggestions in VS Code
next_edit_suggestions: 'next edit suggestions'