[ZBX-23876] Timeout value is missing after changing the type of an existing item Created: 2023 Dec 21  Updated: 2024 Jun 21  Resolved: 2024 Jun 14

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 7.0.0alpha9, 7.0 (plan)
Fix Version/s: 7.0.1rc1, 7.2.0alpha1

Type: Problem report Priority: Trivial
Reporter: Nikita Gogolevs Assignee: Andrejs Griščenko
Resolution: Fixed Votes: 0
Labels: clone, edit, item, items, missing, timeout
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: GIF File timeout-value-edit-issue.gif     PNG File value-timeout.png    
Team: Team A
Sprint: S24-W20/21, S24-W22/23, S24-W24/25
Story Points: 0.25

 Description   

If type of an existing item without timeout (example: Zabbix trapper) was changed to an item type, that has timeout (example: script), the value of the timeout is missing (can be observed when inspecting the page in DevTools), and testing the new item will result in "Unsupported timeout value" error message.
Can be reproduced by editing or cloning the existing item, and changing the type.

Steps to reproduce:
Precondition: item without timeout was previously created (Zabbix trapper or similar)

  1. Open Data collection -> Hosts -> Items
  2. Click on the existing trapper item
  3. Change the type of the item to the type, that has the Timeout parameter, example: Script
  4. Add necessary data, without changing the value of the Timeout
  5. Click test
  6. Click Get value and test

Result:
"Unsupported timeout value" error message is displayed.

See video: 

See screenshot:

Expected:
Value of the timeout should be present, testing of the new item - successful.

 



 Comments   
Comment by Andrejs Griščenko [ 2024 Jun 13 ]

Available in versions:

Generated at Sun Dec 28 15:16:57 EET 2025 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.