Help

alerts

How to View, Filter, and Manage Alerts in devActivity

The devActivity Alerts dashboard is your central hub for monitoring and managing notifications that signal potential operational bottlenecks in your development workflow. This guide will walk you through the steps to effectively view, filter, and manage these alerts, ensuring your team can quickly address issues and maintain efficiency.

devActivity Alerts dashboard showing filters, alerts table, and action buttons.
The devActivity Alerts dashboard with filtering and management options.
  1. Navigate to the Alerts Section

    Access the "Alerts" section directly from your devActivity dashboard. This will take you to the main alerts management page.

  2. Filter Alerts for Specific Focus

    Use the dropdown filters at the top of the page to narrow down your alert list. You can filter by:

    • Team: Focus on alerts relevant to a specific team (e.g., "Demo team 2").
    • Resolved by: See alerts resolved by a particular team member or all.
    • Triggered by: Filter by the source or type of alert.
    • Period: Select a timeframe (e.g., "3 Month") to view alerts within that duration.
    • Status: Choose to view "All", "Done" (resolved), or "Active" alerts.
  3. Review Individual Alerts

    Each row in the alerts table represents a unique alert. Review the details provided:

    • Alert Description: Understand the condition that was triggered (e.g., "More than 10 hours for PR's Cycle Time").
    • Associated Project/Repository & Pull Request IDs: Click on these links (e.g., "#1234") to navigate directly to the source of the issue for more detailed information.
    • Activity Details: Observe icons indicating activity like time elapsed (e.g., "2d") or comment count (e.g., "5").
    • Created Date: See when the alert was first triggered.
    • Resolution Status (DONE): This column indicates if an alert is resolved. A checkmark, a user avatar with a date, or an auto-resolved icon with a date shows the resolution status and who resolved it (if applicable).
  4. Resolve an Individual Alert

    While a direct 'Resolve' button per row isn't explicitly shown, the 'DONE' column indicates resolution. Alerts can be resolved manually by a team member or automatically by devActivity if they become outdated or irrelevant. The column will update to reflect this status, often showing a user's avatar and resolution date or an auto-resolved icon.

  5. Perform Mass Actions on Alerts

    To efficiently manage multiple alerts:

    1. Select multiple alerts by clicking the checkboxes next to each alert description.
    2. Click the "Mark as Done selected" button to resolve all chosen alerts in bulk.
    3. Alternatively, click the "Delete selected" button to remove all chosen alerts from the dashboard.
  6. Monitor Alert Trends

    At the bottom of the Alerts page, observe the graph that visualizes the historical trends of open and closed alerts over several previous months. This chart is a valuable tool for retrospective discussions and continuous process improvement.

By following these steps, you can effectively manage your devActivity alerts, ensuring timely identification and resolution of operational bottlenecks, and fostering a more efficient development workflow.

Track, Analyze and Optimize Your Software DeveEx!

Effortlessly implement gamification, pre-generated performance reviews and retrospective, work quality analytics, alerts on top of your code repository activity

 Install GitHub App to Start
devActivity Screenshot