Server

Overview We're requesting a comprehensive Licensing Insights Dashboard to provide detailed analytics on user activity, track deactivation reasons, and allow permanent exceptions for critical users. Key Requirements: Dashboard Visualization Centralized overview of CircleCI licensing usage Visual charts and graphs showing active/inactive user trends Customizable time period selection User Activity Metrics: Detailed analytics on builds triggered and pipelines executed Usage metrics with filtering by timeframe (daily/weekly/monthly) Activity threshold indicators User Status Tracking: Complete user listing with current status (active/inactive) Detailed deactivation reasons with timestamps Admin accountability for deactivation actions Historical status change logs for auditing Critical User Protection: Ability to designate users as "critical" to prevent automatic deactivation Management interface for critical user list maintenance Confirmation prompts and notifications when critical users are modified Reporting Capabilities: Exportable reports on licensing usage and status changes Real-time data integration with existing CircleCI APIs Scheduled report delivery options Business Objectives: Increase transparency into license utilization Optimize resource allocation by identifying inactive users Maintain security compliance through detailed audit trails Prevent workflow disruptions by protecting essential users This feature will significantly enhance our license management capabilities while ensuring business-critical operations remain uninterrupted.

Summary Currently, when users re-run a workflow or trigger a new pipeline in the CircleCI UI (version 4.7.3), the project home page does not automatically update to show the new workflow/pipeline without manually refreshing the page. This creates a disjointed user experience and adds unnecessary steps to the workflow monitoring process. Current Behavior When a user re-runs a workflow, the UI does not automatically update to show the new workflowUsers must manually refresh the page to see newly triggered workflows/pipelinesThis behavior is inconsistent across the UI - in some contexts, a workflow re-run loads the workflow's jobs view, while in others it does nothing visible until refreshThis issue has been confirmed by CircleCI support as "expected behavior" but represents a suboptimal user experience Requested Feature Implement real-time UI updates so that: When a user re-runs a workflow, the UI automatically updates to show the new workflow without requiring a page refreshThe project home page (with appropriate branch filters) automatically updates when new pipelines are triggered"Following" a project provides a more real-time experience with automatic updatesThe UI behavior is consistent across different contexts within the application User Impact This feature would: Reduce friction in the development workflowEliminate confusion about whether actions have completed successfullySave time by removing unnecessary page refreshesCreate a more responsive, modern application experienceAlign with user expectations for real-time feedback Business Value Implementing this feature would: Improve overall user experienceReduce support inquiries related to this confusing behaviorAlign with modern web application standardsDemonstrate responsiveness to customer feedback Suggested Implementation When a user triggers a workflow re-run, the UI should either: Automatically navigate to the workflow's job view, orRefresh the pipeline's workflow view in place Either approach would provide immediate visual feedback that the action was successful and eliminate the need for manual page refreshes.

Currently, in runner 3.0 if access to download task agent is entirely blocked, the runner will fail. The feature request is to allow existing task-agent to be used as failback option instead of failing.

Ability to SQL tools for monitoring usage and build performance on the platform. Teams need to track build times over specific periods, and it would be highly beneficial to categorize this data by the users who initiate each build. For example ability to get the total duration of build per month, per user, per projects, per executor type, or etc and report to financial team or engineering team for development cost. Currently we relying on direct database queries poses challenges due to potential changes in the database structure. Implementing these features will help teams better manage resources, optimize workflows, and maintain accountability.

This feature request is to enable the ability to allow users and admins to unfollow a project using the UI. This is currently possibly when opening a connection to REPL but requires a query of the database to get a list of followed projects.

In server it can be hard to understand why something didn't run without metrics and logging information, which is stored in the pod logs. It would be great if a scheduled workflow and/or scheduled pipeline (when they make it into server), we show in the UI a error message that could explain why something did not run.

CircleCI Server has a feature to get audit log, but the access logs of web server are not included. "frontend" container of server has the access logs includes gloval IP addresses, so I would be glad if we can download all access logs on WebUI. CCI-I-1333

The self-hosted runner page is cluttered and there's no way to remove runners that we no longer want to support. It would be nice to clean up the page to only see what I want to see

In cloud, small and medium+ docker resource classes automatically map to medium and large remote docker resource classes. It would be great if you could configure this in mapping in Server since you can create your own Docker/Machine resource classes.

Both of CircleCI server3/4 don't support applying for ARM AMI images. (only one AMI image can be configured at the moment) https://circleci.com/docs/server/operator/manage-virtual-machines-with-vm-service/#linux-image-aws There are strong needs for companies already using x86 based AMI images, and want to add ARM customization images as well for users. If we can configure both x86 AMI and ARM AMI images on server4 would be worth it