[ZBXNEXT-8121] Input field for frontend scripts Created: 2022 Nov 28  Updated: 2024 Aug 21  Resolved: 2024 Jan 11

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: API (A), Frontend (F)
Affects Version/s: None
Fix Version/s: 7.0.0alpha9, 7.0 (plan)

Type: New Feature Request Priority: Trivial
Reporter: Mateusz Dampc Assignee: Eliza Sekace
Resolution: Fixed Votes: 6
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified
Environment:

Zabbix Frontend


Attachments: PNG File Screenshot 2023-09-27 at 19.00.46.png     PNG File Screenshot 2023-09-27 at 19.03.43.png     PNG File Screenshot 2023-09-27 at 19.06.51.png     PNG File Screenshot 2023-12-21 at 11.21.44.png     GIF File broken_confirm_popup.gif     PNG File image-2023-11-07-15-16-22-170.png     PNG File image-2023-12-13-13-47-10-820.png     PNG File screenshot-1.png     PNG File screenshot-2.png     PNG File screenshot-3.png     PNG File screenshot-4.png     PNG File screenshot-5.png     PNG File screenshot-6.png     PNG File screenshot-7.png     PNG File screenshot-8.png     PNG File screenshot-9.png     GIF File script_execution.gif     GIF File trigger_context_menu.gif     File zbxnext-8121.yaml    
Issue Links:
Causes
causes ZBX-23874 Map Elements with a URL defined resul... Closed
causes ZBX-25084 "Access denied" to run global script ... Closed
causes ZBX-24042 Undefined array key error appears whe... Closed
Duplicate
is duplicated by ZBXNEXT-5773 Dynamic/Ad-hoc global scripts prompti... Closed
Sub-task
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-8593 Server changes to validate user input... Specification change (Sub-task) Closed Juris Lambda  
Epic Link: Zabbix 7.0
Team: Team D
Sprint: Sprint 103 (Aug 2023), Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), Sprint 106 (Nov 2023), Sprint 107 (Dec 2023), S2401
Story Points: 3

 Description   

I think it would be nice to add new feature to frontend scripts, which will be fimiliar to macros {ALERT.MESSAGE} and {ALERT.SUBJECT}. Because sometimes some frontend scripts requires a few conditions, which cannot be provided by built-in macros. So to do it's required to create few the same frontend scripts, what provides a mess.

I would provide variables (which can be provided in script by new built-in macro e.g {SCRIPT.INPUT}) in "Confirmation message".

Example situtation:

Creating frontend script with type webhook to add new period maintenance in Zabbix. On host menu would be visible action "Create maintenance to this host for X days". After clicking that would be visible popup with text area with custom message eg. : "How long your host should be in maintenance". When intiger value would be provided then this value will be contained in special new built-in macro.

 



 Comments   
Comment by Eliza Sekace [ 2023 Sep 25 ]

Implemented in development branch feature/ZBXNEXT-8593-6.5

Comment by Juris Lambda [ 2023 Dec 18 ]

Available in

Comment by Martins Valkovskis [ 2023 Dec 22 ]

Updated documentation:

<esekace> Updated API documentation:

Generated at Thu Dec 26 08:16:47 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.