In the article about automated email digests you saw how, with just a few clicks, you can create summaries which are sent to you by email. However, when you receive an email digest you must react to it yourself and initiate some further action. In this article we show you how you can automatically react to changes in your problems database, without having to do anything yourself.
So what are Automated Actions?
Automated Actions are small commands which are automatically performed by the system whenever the state of a problem changes – for example if a new error report is received.
Let us illustrate this with an example.
Suppose your team has repaired a problem in your server software and have rolled out the new version. The problem should not reappear again. But what if it does? Then the Error Reporting System should recognise it and inform the developer about it.
The screenshot below shows how you can recognise one such situation with Automated Actions and automatically react to it. An automatic action consists of two parts: (1) several conditions that must be fulfilled at the time of testing and (2) several actions that should then be automatically performed by the System.
The conditions here check for all problems with the status “Closed”, “Verified”, and “Done”, and whether any new error reports for them have arrived since the time of the their last status change. If so, then the bug obviously wasn’t fixed. The problem will than be automatically reopened, or in other words, the problem status will change to “Reopen” and the resolution of the problem will be set to “Unresolved”.
Where can Automated Actions be defined?
Automated Actions can be defined on three different scopes:
- as system-wide actions,
- as project-wide actions, and
- individually for a single problem.
The first two scopes are intended to give an illustration of the general workflows, while the single problem scope is intended for specific situations, for example if a single developer would like to have an email sent if some condition for a certain problem has changed, e.g., when the same error occurred in a later version of the software.
With Automated Actions different work flows can be illustrated and automated. For example, various tags can be defined so that problems can be automatically tagged with them, for example, if a new user comment is received, if the severity of a problem is raised, if the number of reporters of a problem reaches a certain threshold, and many more.
Further information on Automated Actions and many examples can be found in the Automated Actions configuration sections in Ctrlflow Automated Error Reporting Server UI.