Disabled items re-enabling on template change

[waveworksmatt]

Hi,

Apologies if this has been covered but I can't find any reference to it. The problem I have is as follows...

1. I assign a standard template to a host
2. I then view the host and disable any items that I do not want monitoring on that host.

This works fine until I edit an item in the template that I have disabled on a host. Once I make any change to the template item it automatically gets re-enabled on the host which means I have to go through all the hosts I've disabled the item on and re-disable it again.

Is there anyway to prevent disabled items on hosts from being re-enabled automatically whenever the parent item is edited on the template?

Any guidance/comments would be apprecaited.

Thanks,

Matt

[xs-]

AFAIK this has always been the case (in 1.4 and 1.6).
If you think about it, it is kind of logical; all template modifications are passed on to the childs.

I can't think of anything which would prevent this, except code changes.

[waveworksmatt]

I agree with the logic as changes should be propagated to the child hosts.

However, from what I can tell the Item ID remains the same regardless of the changes that are made to the item detail when editing. If this is the case why can't the system check to see which hosts have this item disabled before propagating the changes and turning all items to active?

I'd have thought that it would be a relatively simple check.

[xs-]

agreed

but, the php interface updates status as well and the only way around this would be a code change.

[Alexei]

agreed

but, the php interface updates status as well and the only way around this would be a code change.

We are aware of this issue. I am sure it will be addressed in the next major release, perhaps also back ported to 1.6.x.

[jean]

This modification will be present in 1.8 or not ?

[Alexei]

This modification will be present in 1.8 or not ?

I believe it is already in 1.6.3.