-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: Actions, Conditions, Rule execution (engine)
-
0
Currently, if an issue triggers an automation and does not meet any of the conditions, then no actions are taken, the automation is considered to have completed successfully and reports in the log as Success.
Depending on the conditions of an automation, the majority of executions may appear in the logs as with the status "Success". While this is an appropriate status, it makes it very difficult to find an event where something actually happened. The only way to find the execution that performed any actions is to open every successful event. The duration hints that actions may have been taken, but is not conclusive.
I suggest a simple Action Count that would help an admin filter in/out the automation executions where actions were taken, or where no action was taken. I suggest leaving no actions blank as opposed to showing "0" so no actions taken rows are more obvious.
To recover space needed in the UI for the above perhaps only the Project code needs to be displayed, not also the full project name.
![]()
Suggested change:
![]()
- links to