As we are relentlessly working to improve Coderr, we are excited about the latest changes. Feedback from our users suggested they value the ability to quickly get an understanding of the generated errors in their application. It is also important for Coderr to be adapted to user preferences, providing control and insight along the way.
Coderr’s latest improvements focus on a redesign of how our users want to work, with a clear and clean overview and functions organized in a logical flow. For our Coderr Live and OnPremise users we have also added an improved prioritization function, where you decide how Coderr will organize and display errors. Further, Coderr Live and OnPremise provide information on how different applications releases compare with number of incidents.
These improvements were first made in Coderr Live and then after a Beta-process in Coderr Community Server. In addition, Coderr OnPremise which is now available for evaluation on request also contains them. Why not experience the changes during a free two-week trial with Coderr Live, with no strings attached? You can also download the latest edition of Coderr Community Server of course. To make things easier, we have made the getting started process clearer and organised the instructions better. We recommend all our users to look at the documentation on our site and read postings in our forum. There are further improvements to the user interface planned for summer. Please go to the forum and let us know of your ideas and thoughts.
The overview is central to getting a quick view on what is going on with your application or applications, if you have multiple as shown in the example above. Instead of having a control board rich with capable features and functions, the new overview has given way to relevance and clarity. To the left, there is a summary of your different incidents and in center the graphical display provides a clear view of variation over time. Both parts are organized in time intervals that you can set yourself.
Different functions of Coderr are now organized in a logical flow. From the overview under “Discover”, one would typically want to find out more about what has occurred in the application. In “Analyze” there are further details per each incident where the rich context will provide necessary information for further decision and actions.
Applications can generate many incidents so it is essential to prioritize the work dealing with them. The criteria, or your business rules, can be set to reveal the errors that are the most frequent or oldest. But you can also use criteria which affects most users and easily define your own criteria. Using criteria for prioritizing the incidents bring structure and consistency for everyone involved in application development or performance.
Deployment Insights reveals how earlier changes compare with number of incidents. Are the number of unique errors getting fewer or are they increasing per version? This view show trends in number of errors per version release and if code quality seems to be improving.
In addition, Deployment Insights also provide specific information about the errors per version release. Here you can discover if older errors resurface again or there are new different kinds of errors relating to the specific version release which need attention.