That is a nice idea, but unfortunately it's too much work for me at the moment. I'll need to find some solution that is implementable with little changes to the current implementation. Maybe trying to put the help text at bottom to be descriptive enough is the only thing I can do (?).

But even if that change would be there now, I do consider the blue bar very useful, at least it has been for me. With the blue bar I can with a quick glance see what rules conditions match currently.

I used to have that same kind of help text in other actions too, but the repetition was too much IMO so I removed it from other places than the profile. I thought it is good to be left somewhere, to explain to users how the restore previous functionality works. My idea was the same that you propose, that I'd replace it eventually with a more generic help button that I can include in each page.

Because no one has requested it yet . I've just saved some time not to put it there unless someone needs the functionality. I think it will get there anyway eventually, but faster if someone needs it really.

I know... the length of it sickens me. I have many UI related things I'd like to improve. But as I have very limited time to work on this project, I've had to choose between implementing new functionality and doing the UI plumbing work. So I've delayed the UI work.

But I have thought about that reorganization. I have two ideas how to solve it currently (and I am interested what solution people would prefer).

1) Reorganize the actions into groups like you showed.

2) Keep the flat list, but initially hide all other actions except 2-4 that I deem as most commonly used. Instead there would be "Add more" button or something like that, where you could select more actions to set-up. Once an action that was initially hidden is defined, it will become visible on the main edit page. One option would be also to not have any initially visible actions, but only button "Add action". Another, later option could be to have a settings page where user could himself define what he considers his "favorite" actions that are shown initially.

I'm currently liking the solution number 2 more, but it's a bit of a work.