One topic that pops up from time to time is whether your Ctrlflow Automated Error Reporting server can automatically reopen a problem that was supposed to be fixed but still receives error reports in newer versions of your software. Luckily, Ctrlflow Automated Error Reporting offers a simple yet powerful feature that allows you to do exactly that: Automated Actions.
An automated action consists of a set of conditions that, when satisfied, trigger one or more actions. Suppose you want to automatically reopen a problem that you thought was fixed in version 3.2.1 of your plug-in. To do so, simply go to the problem’s details page and add an automated action which sets the problem’s status to Reopened whenever Ctrlflow Automated Error Reporting receives an error report referencing the plug-in in version 3.2.1 or later:
But automated actions are even more versatile. For instance, you can assign a “needs-review” tag to the problem and set up an email digest that notifies your QA team of all the problems tagged with needs-review. Check out the available actions dropdown and pick your set of actions as needed.
A few additional notes when using automated actions:
- Automated actions are evaluated once per day.
- All configured actions are executed as soon as all conditions are met. Always. So remember to update (or remove) the automated action when it was triggered once (and should only be triggered once).
- In case the problem is linked with a bug tracker, updates to the problem’s status, resolution, and severity are propagated to the bug (along with a comment explaining why it the bug’s state was changed).
- Last but not least, you can specify automated actions per project or per project group. This allows you to easily declare project-wide or system-wide policies like “automatically reopen a problem that occurred in version ≤ 4.5.0.”
Do you have questions about conditions or do you miss an action? Get in contact with our support or on Twitter.