Permissions
Org Admin | Team Manager (for assigned team) | Org Contributor | External Contributor |
View Resolve | View Resolve | View Resolve | No access |
devActivity is a powerful tool for managing developer activity, and its alerts system plays a crucial role in identifying and addressing potential bottlenecks in your development workflow. This article will guide you through the process of managing alerts, utilizing mass actions, and understanding the alerts resolution automation feature.
Overview
The Alerts section in devActivity provides a centralized view of all triggered alerts. You can filter these alerts by various criteria, such as the person who resolved it, the person who triggered it, the time period, and the status. Each alert includes details like the alert name, title, related pull requests, date triggered, and additional data.
Core Features and Functionalities
Viewing and Filtering Alerts
Access the Alerts section: Navigate to the "Alerts" tab in the devActivity dashboard.
Filter by criteria: Use the filter options to narrow down your view. For example, you can filter by "Resolved by" to see alerts resolved by a specific user, or by "Period" to view alerts triggered within a particular timeframe.
Sort alerts: You can sort alerts by "Created" or "Done" to view the most recent or oldest alerts.
Resolving Alerts
Mark as Done: Click on the "Mark as Done" button next to an alert to indicate that it has been resolved.
Mass Actions: Use the "Mark as Done all" or "Mark as Done selected" buttons to resolve multiple alerts in bulk. This is particularly useful when addressing a large number of alerts related to a specific issue or event.
Delete Alerts: If an alert is no longer relevant, you can delete it using the "Delete selected" button.
Alerts Resolution Automation
devActivity features an automated alert resolution system that automatically marks related alerts as "done" when a pull request is merged or closed. This eliminates manual updates and ensures that all relevant alerts are resolved promptly.
Advanced Features
Alert Thresholds
You can configure alert thresholds to define the conditions that trigger an alert. For example, you can set an alert to trigger when a pull request's cycle time exceeds 12 hours. This allows you to identify and address potential issues before they escalate proactively.
Custom Alerts
You can create custom alerts to monitor specific events or conditions relevant to your project. For instance, you could create a custom alert to trigger when a pull request has more than 10 comments, indicating a potential communication bottleneck.
Common Issues and Troubleshooting
Alerts Not Resolving Automatically
Check Pull Request Status: Ensure that the pull request associated with the alert has been merged or closed.
Verify Automation Settings: Confirm that the automated alert resolution feature is enabled in your devActivity settings.
Alerts Triggering Too Frequently
Adjust Alert Thresholds: Review your alert thresholds and adjust them to reduce the frequency of false positives.
Use Challenges: Consider implementing challenges that impact the metrics that are triggering alerts too often. This can help to encourage positive behavior and reduce the number of alerts.
Best Practices and Use Cases
Regularly review alerts: Make it a habit to check the Alerts section regularly to stay informed about potential issues in your development workflow.
Discuss triggered alerts: Use the information from triggered alerts to facilitate discussions during retrospectives. This can help your team identify areas for improvement and prevent similar issues from occurring in the future.
Keep alert thresholds actualized: Regularly review and update your alert thresholds to ensure that they are still relevant and effective. This will help you to identify bottlenecks instantly without being overwhelmed with false or unimportant notifications.
Use challenges to impact alerts: Implement challenges that target the metrics that are triggering alerts too often. This can help to encourage positive behavior and reduce the number of alerts.
Recommendations
Use mass actions for multiple alerts selected to resolve/delete them in bulk.
Triggered alerts and resolution comments are a good thing to discuss on Retrospective.
Keep alert thresholds actualized to identify the bottlenecks instantly but not be overwhelmed with false or unimportant notifications.
Use Challenges to impact the metrics alerting too often.
Share an idea for additional alerts.
By effectively managing alerts, you can proactively identify and address potential issues in your development workflow, improving efficiency and productivity.