Feature Requests

Currently, email notifications can be configured for either "All Builds in My Projects", "My Branches" or "None". It would be very useful to have an option to receive email notifications only for builds I'm the author of, i.e. "My Commits" rather than "My Branches".

The current email notification does not say which part of the build failed when using workflows. You have to click through to the build itself. It'd be great if you could mention the workflow step. CCI-I-324

The ability to send email notification(using CircleCI's notifications feature) to a specific team based on the workflow or job run on CircleCI.

Currently email notification is job/workflow based and it gives status PASSED/FAILED but that doesn't helpful in terms of actual result for certain job. We need test result of particular job irrespective of entire 10 jobs via email notification. CCI-I-906

We'd like to be able to enforce one or more domains for email notifications so private org notifications aren't being sent to employees' personal emails. Our GitHub org already enforces this and CircleCI should be adhering to that restriction or allow us to configure the same restriction.

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.

I would like to disable emails for particular workflows, but not others. This should be configurable within the circleci config.yml. We run automated tests via some workflows and are notified of failures via other means. I would like to disable email notifications for these test workflows. CCI-I-420

Currently I have my personal github linked, My personal github is also what I use with my work repositories since we use github for the workplace as well.I use circleci for my personal projects, and we use circleci for the work repos as well. The downside to this, is my personal email is bombarded with notifications from my work builds if they fail. I also sometimes see a mixture of latest builds from my personal and work environments. It would be nice to just have a little bit more control and separation of teams/groups that I can setup within my user settings. Have failing builds for a particular team/repo go to my work email, while personal projects can go to my personal email. Thank you! CCI-I-887

It would be useful to allow "empty" (need a better name) workflow steps with the following properties: can take part in dependency chains, i.e. can require other jobs to complete can be required by other jobs to complete no build steps and require no build agent to run (similar to "approval" jobs) Such jobs could be useful in structuring and organising workflows.They would save repetition allowing cleaner, DRYer workflow codeand the diagrams would be more unserstandable.For example, imagine the following scenario: 3 build steps which run in parallel when all 3 succeed, you want 3 deploy steps to run in parallel Currently you'd do it like this: workflows: version: 2.1 build_then_deploy: jobs: - build1 - build2 - build3 - deploy1: requires: - build1 - build2 - build3 - deploy2: requires: - build1 - build2 - build3 - deploy3: requires: - build1 - build2 - build3 The resultant, confusing diagram would look like this: build1 --+-- deploy1 |build2 --+-- deploy2 |build3 --+-- deploy3 Adding an "empty" job would allow you to refactor, like this: workflows: version: 2.1 build_then_deploy: jobs: - build1 - build2 - build3 - builds_completed: type: empty requires: - build1 - build2 - build3 - deploy1: requires: - builds_completed - deploy2: requires: - builds_completed - deploy3: requires: - builds_completed The code is more natural to read and the diagram would be less confusing: build1 --+ +-- deploy1 | |build2 --+-- builds_completed --+-- deploy2 | |build3 --+ +-- deploy3 CCI-I-855

Currently email notifications can only be set up for email addresses associated with a GitHub account. We would like to be able to set up email notifications for other email addresses that we do not wish to associate with a specific GitHub account. CCI-I-679