Issue Tracking 2.0
You may remember our quest to introduce light-weight issue tracking capabilities in elmah.io. If not, check out Mark errors as fixed, dashboards and more. Last week we silently launched the next chapter. Before I go into details about the new features, I want to put a few words on issue tracking and elmah.io in general. I'm fully aware of the fact that most (probably all) of you already have an external issue tracker and want to keep it that way. We don't have any plan of offering a replacement for Jira or Azure Boards. The issue tracker built into elmah.io is meant for easier filtering, grouping and rule based actions.
Let me introduce you to the new features. In short, log messages can now be assigned to a developer on your team. There is a new drop-down on the message details view:
The list of users consists of accounts that have access to the log containing the error. This means that you don't need to do additional user administration in order for the this to work.
Once assigned a log message, elmah.io will automatically assign any new instances of the log message to the same user. We use the unique grouping algorithm already implemented on elmah.io to assign developers to log messages.
To view all of the log messages attached to your user, there is a new My errors dashboard available in the drop-down next to the Search tab:
Clicking My errors will show you the unique list of errors assigned your user. To view log messages assigned to another user, click the Add filter button and filter by the Assigned To property:
Since Assigned To is a field on all log messages, you can create rules based on the assigned user as well. Examples of this could be:
- Ignoring all debug messages assigned to a specific user.
- Sending a direct notification to a Slack user when new instances of an error are assigned an elmah.io user.
The easiest way to create rules like this is to add an Assigned To filter from search, click Ignore future messages like this and go to Rules to add the correct action. We want to improve this in the future by letting you create rules directly from search and/or by adding search filters to Rules, but for now this is fastest way of creating rules based on a search result.
As always, let me know what you think. Also, there is a new landing page with some longer explanations of the features mentioned above: Issue Tracking - Manage bugs where they are logged.
We monitor your websites
We monitor your websites for crashes and availability. This helps you get an overview of the quality of your applications and to spot trends in your releases.
We notify you
We notify you when errors starts happening using Slack, Microsoft Teams, mail or other forms of communication to help you react to errors before your users do.
We help you fix bugs
We help you fix bugs quickly by combining error diagnostic information with innovative quick fixes and answers from Stack Overflow and social media.