# Getting Personalized Feedback
As opposed to many existing static analyses tools, Teamscale strives to provide immediate feedback for developers. Personal and quick feedback is essential when trying to improve quality .
We have often seen that the absence of it causes quality improvement campaigns to fail. Teamscale employs its analyses commit-based and is, thus, able to provide fine-grained feedback. Feedback which does not overflood the developer but instead focuses on his specific need. And feedback which comes quick enough while he is still working on his task.
# Inspecting the Impact of a Single Change
Developers can use Teamscale in several different ways to get feedback: In the activity perspective of the Web UI, they can inform themselves about the impact of their recent commits. If developers want to avoid context switches, they can stay in their IDEs and use Teamscale's integration. Or, they can turn on the email service and receive notifications when something noteworthy happens.
In the activity perspective, developers can browse the commit history of the underlying version control system:
# Developer Feedback in the Activity Perspective
They can directly glance at the most recent commits at the top of the stream or use the filter mechanism in the sidebar to view only those changes that were committed by himself, for example. The commit stream provides the technical information about the commit itself (author, message, date and related issue) but also its impact on the system's quality: It shows how many findings were added by this commit (red), how many were removed (green) and how many still remain in code that was modified by this commit.
By clicking on the commit, developers gets more detailed feedback:
# Feedback in Commit Details
They can inspect which findings in which file were added or removed and also which impact their commit had on various metrics. They can then either click on the findings message to navigate to the finding's detail page providing more information about the type of the finding and why it is relevant or click on the finding location to directly jump into the source code.
Inspecting the impact of your change in the browser, however, requires the developer to actively pull this information. Teamscale also provides push-notification services in your IDE and and via email.
# Being Informed Without Leaving Your IDE
Rather than switching to the browser, developers often prefer to gather all necessary information within their IDE. Teamscale integrates in common development environments such as Eclipse, Visual Studio and IntelliJ. With the plug-in, you can inspect the findings directly as markers in the code. To clean up on-the-fly or to inspect newly introduced findings, developers do not have to leave their IDE. Thus, they can avoid distracting context switches.
# Push Notifications: Receiving Emails about Changes
Furthermore, you can configure Teamscale to notify you via e-mail or on your desktop. It remains up to you, about what kind of changes you want to be alerted.
To configure your notifications, click on your user symbol in the upper right corner of the browser and select My Profile in the drop down menu. Then you can select the Notification Rules page in the side bar menu:
You can activate or deactivate desktop notifications by using the check box Enable desktop notification:
In terms of email notifications, you can add rules to be notified when a certain type of finding is added, when a metric threshold is violated or when you are related to a task.
# Editing a Notification Rule for Findings
The image shows an example of the configuration dialog to add a notification rule for findings. You can configure the projects on which the rules applies as well as committers and events triggering the rule. You can also explicitly sate to not trigger the rule if, e.g., the finding category or the finding group equal your specified string. To look up how your categories are named and which groups you are using, please refer to your analysis profile.