Maintenance Period on Trigger/service level (ZBXNEXT-413)

[ZBXNEXT-4572] Frontend: Maintenance Period on Trigger/service level Created: 2018 May 28  Updated: 2024 Apr 10  Resolved: 2018 Aug 27

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0.0beta1, 4.0 (plan)

Type: Specification change (Sub-task) Priority: Trivial
Reporter: Rostislav Palivoda Assignee: Andrejs Griščenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Selection_009.png     PNG File Selection_010.png     PNG File Selection_011.png     PNG File Selection_012.png     PNG File Selection_014.png     PNG File compact.png     PNG File delete_maintenance.png     PNG File hosts and groups.png     PNG File maintenance_icon_size.png     PNG File till_when.png     PNG File time.png    
Issue Links:
Causes
causes ZBX-15386 Zabbix Trigger overview - not showing... Closed
causes ZBX-15435 Error message on Dashboard Closed
causes ZBX-15778 Wrong filtering by "Age less than" an... Closed
Sub-task
depends on ZBXNEXT-4672 Add "Show suppressed problems" to Mon... Closed
part of ZBX-14711 Triggers in trigger overview being fi... Closed
Team: Team A
Sprint: Sprint 34, Sprint 35, Sprint 36, Sprint 37, Sprint 38, Sprint 39, Sprint 40, Sprint 41
Story Points: 10

 Description   

See parent task. Spec PDF will be attached when ready. 

 Comments   
Comment by Andrejs Griščenko [ 2018 Jul 16 ]

(15) [D] Updated API documentation:

iivs

  • Action object
    • This "16 - maintenance status" is no longer true.
    • This "16 Maintenance status in, not in No value required: using the “in” operator means that the host must be in maintenance, “not in” - not in maintenance." is also false.
    • New condition operator is not described.
  • Event object and Problem object
    • I'm having doubts about word "(default)". It's not a DB field, so it cannot have a default value.
  • event.get and problem.get
    • First figure out (18) and then we will see if it's boolean or something else.
    • Don't use different formatting styles for "(string)".
  • maintenance.create and maintenance.get
    • I'm having doubts that "tag1" and "value1" are good examples.
    • Shouldn't the "Creating a maintenance" description contain some information about tags and why they are created what effect it will have? And "Retrieving maintenances" description could also have tags mentioned, since those are requested.
  • (map API will be reviewed after implementation)

REOPENED

agriscenko RESOLVED

iivs Changes are not mentioned at all. And before resolving this sub-issue, please, finish map API and write all the changes.

REOPENED

agriscenko RESOLVED

iivs

  • New changes should go on top.
  • "Other changes and bug fixes" -> "action" -> "changes": API doesn't understand what Yes and No operators are. API accepts integers.
  • "Other changes and bug fixes" -> "event/problem" -> "changes": Possibly you could split into two lines, because those two properties have two different meanings.
  • "Other changes and bug fixes" -> "maintenance" -> "changes": Separate methods by comma, just like in other places. Be mindful of words like "parameter", because I think "selectTags" is an "option", but "tags" is property. Check wording.

REOPENED

agriscenko RESOLVED

iivs CLOSED

Comment by Alexander Vladishev [ 2018 Aug 27 ]

Available in 4.0.0beta1 r84123

Generated at Sat Apr 27 04:32:35 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.