Also, if we create a new action operation, the operation type defaults to "Send message" and "Default message" checkbox is checked. If we change the operation type to "Remote command" and to "Send message" back again, the "Default message" checkbox becomes unchecked.

Aleksandrs Saveljevs
added a comment - 2010 Jun 30 15:10 Similarly, "
{TRIGGER.NAME}
:
{STATUS}
" is probably not the best example of a remote command.
Also, if we create a new action operation, the operation type defaults to "Send message" and "Default message" checkbox is checked. If we change the operation type to "Remote command" and to "Send message" back again, the "Default message" checkbox becomes unchecked.

(1) If we attempt to create a discovery action, then both the subject and body say "DISCOVERY". If we change action type to "Auto registration", then they both become "AUTOREG". If we change action type to "Triggers", they become the defaults for trigger actions. However, if we now change the action type to "Discovery", then the body will not change.

<asaveljevs> Also, the implemented approach is that the subject will change independently of the body. That means that if a user has changed subject, but not the body, only the body will change. Perhaps, we should look at subject and body together - change them if both are at the defaults.

Aleksandrs Saveljevs
added a comment - 2011 Oct 17 17:30 - edited (1) If we attempt to create a discovery action, then both the subject and body say "DISCOVERY". If we change action type to "Auto registration", then they both become "AUTOREG". If we change action type to "Triggers", they become the defaults for trigger actions. However, if we now change the action type to "Discovery", then the body will not change.
<asaveljevs> Also, the implemented approach is that the subject will change independently of the body. That means that if a user has changed subject, but not the body, only the body will change. Perhaps, we should look at subject and body together - change them if both are at the defaults.
<Vedmak> RESOLVED
<asaveljevs> CLOSED

In trunk dev branch ZBX-2493 (rev #22612) all is fine, BUT when using IE8 browser several user groups can overlap each over on the screen, please see screenshot for more details. Some time ago (when I was testing maintenance periods) I also registered appropriate issue: ZBX-4244

Igor Danoshaites
added a comment - 2011 Oct 21 17:40 In trunk dev branch ZBX-2493 (rev #22612) all is fine, BUT when using IE8 browser several user groups can overlap each over on the screen, please see screenshot for more details. Some time ago (when I was testing maintenance periods) I also registered appropriate issue: ZBX-4244