diff --git a/docs/organizations/notifications/includes/opt-out-notification.md b/docs/organizations/notifications/includes/opt-out-notification.md index 722e831401a..5de90fb7360 100644 --- a/docs/organizations/notifications/includes/opt-out-notification.md +++ b/docs/organizations/notifications/includes/opt-out-notification.md @@ -9,7 +9,7 @@ ms.date: 06/22/2023 ## Unsubscribe or opt out of a team or out-of-box (OOB) notification subscription -You can choose to not receive notifications for certain team notification subscriptions by opting out. +You can opt out of receiving notifications for specific team notification subscriptions. ::: moniker range="azure-devops" @@ -32,4 +32,13 @@ To unsubscribe from any notification, slide the state **On/Off** indicator to th ::: moniker-end > [!NOTE] -> Whether or not you're an administrator, when you move the toggle for a shared team notification subscription in your settings only impacts you and not other team members. +> Whether you're an administrator or not, toggling for a shared team notification subscription in your settings only affects your notifications, not those of other team members. + +## Disable work item notifications for a project + +To override organization settings and disable all work item notifications for a project in Azure DevOps, do the following steps: + +1. Sign in to your project (`https://dev.azure.com/{Your_Organization/Your_Project}`). +2. Select **Project settings** > **Notifications**. +3. Highlight the Work notification and select :::image type="icon" source="../../../media/icons/gear_icon.png" border="false"::: **Delivery settings**. +4. Choose **Do not deliver** and **Save**. diff --git a/docs/organizations/notifications/manage-team-group-global-organization-notifications.md b/docs/organizations/notifications/manage-team-group-global-organization-notifications.md index 0e21ca30d12..a5aead4d82a 100644 --- a/docs/organizations/notifications/manage-team-group-global-organization-notifications.md +++ b/docs/organizations/notifications/manage-team-group-global-organization-notifications.md @@ -1,5 +1,5 @@ --- -title: Manage notifications for a team, project, organization or collection +title: Manage notifications for a team, project, organization, or collection titleSuffix: Azure DevOps description: Learn how to configure team, project, and organization/collection notifications for when changes occur to source code, git, work items, and builds in Azure DevOps. ms.subservice: azure-devops-notifications @@ -8,7 +8,7 @@ ms.custom: cross-project ms.author: chcomley author: chcomley ms.topic: how-to -ms.date: 04/24/2023 +ms.date: 09/05/2024 monikerRange: '<= azure-devops' --- @@ -175,14 +175,12 @@ Choose to allow or block delivery of emails for all subscriptions owned by a tea ::: moniker-end - - [!INCLUDE [opt-out-notification](includes/opt-out-notification.md)] ## Related articles -- [Manage personal notification settings](manage-your-personal-notifications.md) -- [Set your preferences](../../organizations/settings/set-your-preferences.md) -- [Default and supported notifications](oob-built-in-notifications.md) -- [Follow a specific work item](../../boards/work-items/follow-work-items.md) +- [Manage your personal notification settings](manage-your-personal-notifications.md) +- [Set your notification preferences](../../organizations/settings/set-your-preferences.md) +- [Review default and supported notifications](oob-built-in-notifications.md) +- [Follow a specific work item](../../boards/work-items/follow-work-items.md) - [Change your preferred email address](change-email-address.md) diff --git a/docs/organizations/projects/delete-project.md b/docs/organizations/projects/delete-project.md index c7f3556bd0d..bfbee4acc30 100644 --- a/docs/organizations/projects/delete-project.md +++ b/docs/organizations/projects/delete-project.md @@ -9,7 +9,7 @@ ms.topic: conceptual ms.author: chcomley author: chcomley monikerRange: '>= azure-devops-2019' -ms.date: 12/05/2023 +ms.date: 09/05/2024 --- # Delete a project @@ -19,22 +19,25 @@ ms.date: 12/05/2023 If a project becomes obsolete, you can [delete it](#delete-project) from your organization or collection in Azure DevOps. Likewise, if you're migrating from an on-premises Azure DevOps Server to Azure DevOps Services, it might be necessary to delete the project. The removal of projects can also enhance navigation by restricting it to only those projects that are currently in use. > [!CAUTION] -> Projects deleted from the web portal are soft-deleted and permanently removed if not restored within 28 days. However, projects deleted from the on-premises Azure DevOps Administration Console are hard-deleted and can't be restored. For restoration details, see [Restore a project](#restore-a-deleted-project). To access data from a deleted project without restoring it, [save project data](#save-project-data). +> - When you soft-delete projects from the web portal, they're permanently removed if not restored within 28 days. +> - When you hard-delete projects from the on-premises Azure DevOps Administration Console, you can't restore them. +> For more information, see [Restore a project](#restore-a-deleted-project) and [Save project data](#save-project-data). ## Prerequisites ::: moniker range="azure-devops" -* You must be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group. -* You must have the **Delete team project** permission set to **Allow**. For more information, see [View project-level permissions](../security/view-permissions.md#view-project-level-permissions). -* (Optional) [Save project data](#save-project-data) before you delete a project if you want to access project data without restoring it. +* **Permissions:** + * Be a member of the [Project Collection Administrators group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group. + * Have the **Delete team project** permission set to **Allow**. For more information, see [View project-level permissions](../security/view-permissions.md#view-project-level-permissions). +* **Optional:** [Save project data](#save-project-data) before deleting a project if you want to access project data without restoring it. ::: moniker-end ::: moniker range=" < azure-devops" -* To restore a project, you must have the **Delete team project** permission set to **Allow**. For more information, see [View permissions](../security/view-permissions.md). -* (Optional) [Save project data](#save-project-data), as deleting a project results in irreversible data loss. +* **Permissions:** Have the **Delete team project** permission set to **Allow**. For more information, see [View permissions](../security/view-permissions.md). +* **Optional:** [Save project data](#save-project-data), as deleting a project results in irreversible data loss. ::: moniker-end @@ -176,7 +179,7 @@ If you inadvertently delete a project in Azure DevOps, you can restore it within 3. Select **Overview**, and then scroll down to "recently deleted projects." - ![Screenshot that shows recently deleted projects.](../accounts/media/shared/organization-settings-select-overview.png) + ![Screenshot that shows recently deleted projects.](media/delete-project/recently-deleted-projects.png) 4. Highlight the project you want to restore, and then select **Restore**. @@ -284,4 +287,4 @@ A: Wait 28 days before the project is permanently deleted. - [Create a project](create-project.md) - [Restore a project](delete-project.md#restore-a-deleted-project) - [Delete a project with REST API](/rest/api/azure/devops/core/projects/delete) -- [TFSDeleteProject command line tool](/azure/devops/server/command-line/tfsdeleteproject-cmd) +- [ Use the TFSDeleteProject command line tool](/azure/devops/server/command-line/tfsdeleteproject-cmd) diff --git a/docs/organizations/projects/media/delete-project/recently-deleted-projects.png b/docs/organizations/projects/media/delete-project/recently-deleted-projects.png new file mode 100644 index 00000000000..2ffb289abd9 Binary files /dev/null and b/docs/organizations/projects/media/delete-project/recently-deleted-projects.png differ diff --git a/docs/organizations/projects/media/restore-project/recently-deleted-projects.png b/docs/organizations/projects/media/restore-project/recently-deleted-projects.png index 3f54b712bf3..611bae935cd 100644 Binary files a/docs/organizations/projects/media/restore-project/recently-deleted-projects.png and b/docs/organizations/projects/media/restore-project/recently-deleted-projects.png differ diff --git a/docs/organizations/settings/work/object-limits.md b/docs/organizations/settings/work/object-limits.md index 5cb685ce169..fbf59854fa0 100644 --- a/docs/organizations/settings/work/object-limits.md +++ b/docs/organizations/settings/work/object-limits.md @@ -9,7 +9,7 @@ ms.author: chcomley author: chcomley ms.topic: conceptual monikerRange: "<= azure-devops" -ms.date: 08/19/2024 +ms.date: 09/05/2024 --- # Work tracking, process, and project limits @@ -71,7 +71,7 @@ When you work with teams, work item tags, backlogs, and boards, the following op | User interface | Limit | |--------|-------| | Backlogs | 10,000 work items | -| Boards | 1,000 cards (excluding those cards in the *[Proposed](../../../boards/work-items/workflow-and-state-categories.md)*[ and ](../../../boards/work-items/workflow-and-state-categories.md)*[Completed](../../../boards/work-items/workflow-and-state-categories.md)*[workflow state categories](../../../boards/work-items/workflow-and-state-categories.md)) | +| Boards | 1,000 cards (excluding those cards in the *Proposed* and *Completed* [workflow state categories](../../../boards/work-items/workflow-and-state-categories.md)) | | Taskboard | 1,000 tasks | | Area Paths | 10,000 per project | | Area Path Depth | 14 | @@ -79,8 +79,8 @@ When you work with teams, work item tags, backlogs, and boards, the following op | Iteration Paths | 10,000 per project | | Iteration Path Depth | 14 | | Iteration Paths per team | 300 | -| Project Dashboards | 500 per project | -| Team Dashboards | 500 per team | +| Project Dashboards | 500 per project. Accessible at the project level and anyone with access to the project can use. | +| Team Dashboards | 500 per team. Specific to the team and used to track team-specific metrics and data. | | Teams | 5,000 per project | | Work item tags | 150,000 tag definitions per organization or collection | | Delivery plans per project | 1,000 | @@ -88,6 +88,14 @@ When you work with teams, work item tags, backlogs, and boards, the following op Each backlog can display up to 10,000 work items. This limit applies to what the backlog can display, not to the number of work items you can define, as there's no specific limit. If your backlog exceeds this limit, consider adding a team and moving some work items to the new team's backlog. +> [!TIP] +> If you're approaching the dashboards limits, see the following steps to manage and clean up your dashboards: +> - **Review usage:** Identify dashboards that are no longer in use or are duplicates. You can do this by checking the last accessed date or by consulting with team members. +> - **Consolidate dashboards:** Combine similar dashboards to reduce the total number. This can be done by adding multiple widgets to a single dashboard. +> - **Archive old dashboards:** If certain dashboards are no longer needed but you want to keep the data, consider exporting the data and archiving the dashboards. +> - **Use the Object Limit Tracker feature:** Provides real-time visibility into resource usage, including dashboards. This feature can help you [proactively manage your limits and avoid potential issues](https://devblogs.microsoft.com/devops/introducing-object-limit-tracker-in-azure-devops/). + + #### Other notes: - Completed or closed work items don't display on backlogs and boards once their **Changed Date** is older than a year. You can still list these items using a query. To make them show up on a backlog or board, make a minor change to reset the display clock. @@ -126,7 +134,7 @@ For the On-premises XML process model, you can modify the backlog and Taskboard Azure DevOps Services limits each organization to 1,000 projects per organization, an increase over the previous limit of 300 projects. > [!NOTE] -> Above 300 projects, certain experiences, like connecting to a project from Visual Studio, may degrade. For on-premises Azure DevOps Server, there are no hard limits, but performance issues may arise as the number of projects nears 300. When migrating to Azure DevOps Services, observe the maximum limit of 1,000 projects. If your collection exceeds this limit, split the collection or delete older projects. +> Above 300 projects, certain experiences, like connecting to a project from Visual Studio, might degrade. For on-premises Azure DevOps Server, there are no hard limits, but performance issues may arise as the number of projects nears 300. When migrating to Azure DevOps Services, observe the maximum limit of 1,000 projects. If your collection exceeds this limit, split the collection or delete older projects. For more information, see [Migrate data from Azure DevOps Server to Azure DevOps Services](../../../migrate/migration-overview.md). @@ -136,7 +144,7 @@ Many limits are imposed on the number of objects you can define for a process. F ::: moniker range="azure-devops" -The following table lists the maximum number of objects you can define for the Inheritance and Hosted XML process models. While these are hard limits, practical limits might also apply. +The following table lists the maximum number of objects you can define for the Inheritance and Hosted XML process models. While these limits are hard limits, practical limits might also apply. | Object | Inheritance | Hosted XML | | --------------------------------------------------- | ----------: | ---------: | @@ -165,7 +173,7 @@ For other restrictions and conformance requirements of the Hosted XML process mo ::: moniker range=">= azure-devops-2019 < azure-devops" -The following table lists the maximum number of objects you can define for the Inheritance and On-premises XML process models. While these are hard limits, practical limits might also apply. +The following table lists the maximum number of objects you can define for the Inheritance and On-premises XML process models. While these limits are hard limits, practical limits might also apply. | Object | Inheritance | On-premises XML | | --------------------------------------------------- | ----------: | ---------: | @@ -195,7 +203,7 @@ To minimize performance issues, we recommend following this guidance: ::: moniker range="azure-devops" - Limit the number of custom fields you define. All custom fields contribute to the total allowed for a process, collection, or organization. You can specify different behaviors, such as rules and picklists, for the same field in different WITs. -- Limit the number of rules you define for a WIT. While you can create multiple rules for a WIT, additional rules can negatively affect performance when users add or modify work items. When users save work items, the system validates all rules associated with the fields for that work item type. In some cases, the rule validation expression may be too complex for SQL to evaluate efficiently. +- Limit the number of rules you define for a WIT. While you can create multiple rules for a WIT, other rules can negatively affect performance when users add or modify work items. When users save work items, the system validates all rules associated with the fields for that work item type. In some cases, the rule validation expression might be too complex for SQL to evaluate efficiently. - Limit the number of custom WITs you define. ::: moniker-end @@ -203,9 +211,9 @@ To minimize performance issues, we recommend following this guidance: ::: moniker range="< azure-devops" - Limit the number of custom fields you define. All custom fields contribute to the total allowed for a process, collection, or organization. You can specify different behaviors, such as rules and picklists, for the same field in different WITs. -- Limit the number of rules you define for a WIT. While you can create multiple rules for a WIT, additional rules can negatively affect performance when users add or modify work items. When users save work items, the system validates all rules associated with the fields for that work item type. In some cases, the rule validation expression may be too complex for SQL to evaluate efficiently. +- Limit the number of rules you define for a WIT. While you can create multiple rules for a WIT, other rules can negatively affect performance when users add or modify work items. When users save work items, the system validates all rules associated with the fields for that work item type. In some cases, the rule validation expression might be too complex for SQL to evaluate efficiently. - Limit the number of custom WITs you define. -- Limit the number of reportable fields you define. Reportable fields can impact the performance of your data warehouse. +- Limit the number of reportable fields you define. Reportable fields can affect the performance of your data warehouse. ::: moniker-end @@ -216,9 +224,9 @@ To minimize performance issues, we recommend following this guidance: ## Rate limits -To reduce costs and enhance scalability and performance, Azure DevOps Services, like many Software-as-a-Service solutions, uses multi-tenancy. To ensure good performance and minimize the risk of outages, Azure DevOps Services limits the resources individuals can consume and the number of requests they can make to certain commands. When these limits are exceeded, subsequent requests may be delayed or blocked. +To reduce costs and enhance scalability and performance, Azure DevOps Services, like many Software-as-a-Service solutions, uses multi-tenancy. To ensure good performance and minimize the risk of outages, Azure DevOps Services limits the resources individuals can consume and the number of requests they can make to certain commands. When these limits are exceeded, subsequent requests might be delayed or blocked. -Most rate limits are reached through REST API calls or non-optimized queries. For more information, see [Rate limits](../../../integrate/concepts/rate-limits.md) and [Best practices (to avoid hitting rate limits)](../../../integrate/concepts/integration-bestpractices.md). +Most rate limits are reached through REST API calls or nonoptimized queries. For more information, see [Rate limits](../../../integrate/concepts/rate-limits.md) and [Best practices (to avoid hitting rate limits)](../../../integrate/concepts/integration-bestpractices.md). ::: moniker-end @@ -236,20 +244,20 @@ For more information, see [Migrate data from Azure DevOps Server to Azure DevOps ::: moniker range="azure-devops" -- [About process customization and inherited processes](inheritance-process-model.md) -- [Create an Inheritance process](manage-process.md) -- [Best practices](../../../integrate/concepts/integration-bestpractices.md) -- [Naming restrictions and conventions](../naming-restrictions.md) +- [Learn about process customization and inherited processes](inheritance-process-model.md) +- [Create an inheritance process](manage-process.md) +- [Follow best practices](../../../integrate/concepts/integration-bestpractices.md) +- [Adhere to naming restrictions and conventions](../naming-restrictions.md) ::: moniker-end ::: moniker range=" < azure-devops" - [Customize your work tracking experience](../../../reference/customize-work.md) -- [About process customization and inherited processes](inheritance-process-model.md) -- [On-premises XML process customization](../../../reference/on-premises-xml-process-model.md) -- [Rules and rule evaluation](../../../organizations/settings/work/rule-reference.md) -- [Naming restrictions and conventions](../naming-restrictions.md) +- [Learn about process customization and inherited processes](inheritance-process-model.md) +- [Customize on-premises XML processes](../../../reference/on-premises-xml-process-model.md) +- [Understand rules and rule evaluation](../../../organizations/settings/work/rule-reference.md) +- [Follow naming restrictions and conventions](../naming-restrictions.md) ::: moniker-end diff --git a/docs/user-guide/troubleshoot-connection.md b/docs/user-guide/troubleshoot-connection.md index 60d5dc81f77..f648b26513e 100644 --- a/docs/user-guide/troubleshoot-connection.md +++ b/docs/user-guide/troubleshoot-connection.md @@ -6,7 +6,7 @@ ms.subservice: azure-devops-new-user ms.author: chcomley author: chcomley ms.topic: troubleshooting -ms.date: 01/08/2024 +ms.date: 09/05/2024 monikerRange: '<= azure-devops' --- @@ -18,7 +18,7 @@ monikerRange: '<= azure-devops' ## Troubleshoot connectivity -Complete the following steps to resolve connectivity issues. +To resolve connectivity issues, complete the following steps: 1. Sign out of your browser. To do so, select the [Visual Studio sign out](https://aka.ms/VsSignout) link. 2. Delete the cookies in your browser. To delete cookies in most browsers, select **Ctrl**+**Shift**+**Delete**. @@ -87,7 +87,7 @@ When you get redirected back to the original sign-in page, we recommend that you |-------------|----------------| |You don't have an active account or license.|Check with your administrator that you're a member of the account and have an active, valid license. For more information, see [Assign licenses to users](../organizations/accounts/add-organization-users.md).| |Your Azure DevOps Services organization is connected to the Microsoft Entra ID.|When your Azure DevOps Services organization is connected to a directory that is associated with a Microsoft 365 or Microsoft Azure subscription, only members in the directory can access the account.

Check with your directory administrator to have them [create an organizational account for you or add your account to the directory as external member](/azure/active-directory/active-directory-create-users).| -|You can't switch between different organizational accounts.|If you work with several organizations that connect to different directories, such as accounts created from the Microsoft Azure portal, the sign out function might not work as expected. For example, you can't switch between different organizational accounts to connect to multiple accounts that are linked to directory tenants.

When this problem occurs, you see a flashing blank sign in dialog box several times. Then, you receive either TF31002 or TF31003 error after you connect to or add a new connection in the dialog box.

To resolve this problem, apply the most recent [Visual Studio update](https://visualstudio.microsoft.com/downloads) .

For more information, see [You can't switch between different organizational accounts in Visual Studio Codespace](/troubleshoot/visualstudio/general/cannot-switch-accounts).| +|You can't switch between different organizational accounts.|If you work with several organizations that connect to different directories, such as accounts created from the Microsoft Azure portal, the sign out function might not work as expected. For example, you can't switch between different organizational accounts to connect to multiple accounts that are linked to directory tenants.

When this problem occurs, there's a flashing blank sign in dialog box. Then, you receive either TF31002 or TF31003 error after you connect to or add a new connection in the dialog box.

To resolve this problem, apply the most recent [Visual Studio update](https://visualstudio.microsoft.com/downloads) .

For more information, see [You can't switch between different organizational accounts in Visual Studio Codespace](/troubleshoot/visualstudio/general/cannot-switch-accounts).| |You want to sign in to Azure DevOps Services from Visual Studio using different credentials.|See [Connect to projects, Sign in with different credentials](../organizations/projects/connect-to-projects.md).| ::: moniker-end @@ -103,10 +103,11 @@ Here's a list of the most frequently reported connection problems and what to do 2. Verify that your computer is connected to the network and that it can access network resources. 3. Verify that Azure DevOps Server isn't offline. Check with your Azure DevOps Server administrator. 4. Check whether your project was moved to another project collection in Azure DevOps Server. If it was moved, you must create a connection to the new server name. +5. Verify you're using a [supported version of Azure DevOps Server](/azure/devops/server/requirements). ## TF31002: Unable to connect -If you determine that you're receiving this error from one computer but not others, or others aren't receiving this error, then check the following resolutions. +If you get this error from one computer but not others, or others aren't receiving this error, then check the following resolutions. |Problem|Resolution| |-------------|----------------| @@ -114,8 +115,8 @@ If you determine that you're receiving this error from one computer but not othe |You entered an incorrect server URL.|Verify that you entered the server URL correctly including the server name, port number, and protocol (http/https). For more information, see [Connect to projects](../organizations/projects/connect-to-projects.md).| |The configuration changed.|If the configuration for the on-premises Azure DevOps Server changed, you must create a new connection. You might also need to [clear the client cache](../organizations/projects/connect-to-projects.md).| |You work remotely and need to connect to an Azure DevOps Proxy server to check in files to Azure DevOps Server version control.| [Configure Visual Studio to connect to Azure DevOps Proxy](../organizations/projects/connect-to-projects.md).| -|You're connecting to a later version of Azure DevOps Server than your Visual Studio client version.|Your version of Visual Studio or Team Explorer might be incompatible with Azure DevOps Server. You might need to install one or more GDR packs. For more information, see [Requirements and compatibility](/azure/devops/server/requirements).| -|Your firewall is blocking Azure DevOps services.|See [Allow a program to communicate through Windows Firewall](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766312(v=ws.10)).| +|You're connecting to a later version of Azure DevOps Server than your Visual Studio client version.|Your version of Visual Studio or Team Explorer might be incompatible with Azure DevOps Server. You might need to install one or more General Distribution Release (GDR) packs. For more information, see [Requirements and compatibility](/azure/devops/server/requirements).| +|Your firewall is blocking Azure DevOps.|See [Allow a program to communicate through Windows Firewall](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766312(v=ws.10)).| |Visual Studio stops responding when you run a query in Visual Studio.|Your computer might be configured to bypass the proxy server. Verify the configuration of the BypassProxyOnLocal setting on your computer. For more information, see [BypassProxyOnLocal Configuration](/previous-versions/visualstudio/visual-studio-2008/ee248646(v=vs.90)).| ### Several users can't connect to Azure DevOps Server @@ -126,7 +127,7 @@ As an administrator, check the event logs for the application-tier server to try |Problem|Resolution| |-------------|----------------| -|The *TFSService* account password expired or is incorrect.|Many services for Azure DevOps Server stop running when the service account expires. For more information, see [Change the service account or password for Azure DevOps Server](/azure/devops/server/admin/change-service-account-password).| +|The *TFSService* account password is expired or incorrect.|Many services for Azure DevOps Server stop running when the service account expires. For more information, see [Change the service account or password for Azure DevOps Server](/azure/devops/server/admin/change-service-account-password).| |The application-tier server for Azure DevOps Server is unavailable.|Verify whether each required service is running. If a required service isn't running, you must restart it. If necessary, set it to start automatically. For more information, see [Stop and start services, application pools, and websites](/azure/devops/server/admin/stop-start-services-pools).| |The network is unavailable.|Verify whether your network is operational.| |A website identity for Azure DevOps Server is configured incorrectly.|Verify or correct the server binding assignments that are made to websites for Azure DevOps Server. |