Server

Currently, as the doc mentioned, the job maximum runtime is 5 hours, and no option to change it. https://circleci.com/docs/2.0/configuration-reference/#jobs > Jobs have a maximum runtime of 5 hours.Server customers, especially static install, they don't need to care about the price of the time of running instances. And some machine learning builds need more than 5 hours. CCI-I-1436

We had some very old jobs stuck in "queued" state for months, which were clearly never going to run. These jobs were not present on any nomad nodes, but could be seen via the API and the web UI. When I asked support how to get rid of them, they gave me instructions for how to use kubectl exec to log into a frontend pod and use the REPL to run circle.http.api.admin-commands/force-cancel-build on each job. That worked, but there should be a button on the frontend web UI to do the same thing. Jobs on Server can get lost into this kind of zombie state, and it's not practical to expect people to run a REPL directly on the frontend pod to clear them out - and it's also more risky to do so.

We would like the ability to place a customized HTML banner on specific pages on Server. CCI-I-1191

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

At the moment, the CircleCI color output does not match the same as the docker run and some colors are missing. As an example, please see the photos below. The first photo is the CircleCI behavior and the second one is the expected behavior.

Please allow masking of secret values (environment variables) on CircleCI Server installations. It is important to mask these values in the UI build output. CCI-I-1637

Currently, the Email Notification section on Server 3.x admin only allows for the SMTP server configuration. It would be great to allow Server customers to customize the email content of email notifications (e.g., when builds fail). This can allow customers to localize the content, for example.

We experienced a couple of incidents recently and looking for a feature that notifies end-users on UI when incidents occur on Server 3. The end-users are not seeing any failed jobs or error messages when they had an incident (Related to their Rabbit MQ)and end-users just kept seeing queue jobs. So those end-users weren't sure if it was an incident or any kind of error. It will be nice if they get some notifications or failed jobs with error messages.

Existing Customers often request a better experience with user management. Typically: Deleting multiple users at once Filter active users **Better clarification in the UI of what an "active" user means

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.