[ZBX-21264] SLA report related issues Created: 2022 Jun 28  Updated: 2024 Apr 10  Resolved: 2022 Aug 31

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: API (A), Frontend (F)
Affects Version/s: 6.0.6rc1, 6.2.0rc2
Fix Version/s: 6.0.9rc1, 6.2.3rc1, 6.4.0alpha1, 6.4 (plan)

Type: Problem report Priority: Trivial
Reporter: Sergejs Olonkins Assignee: Andrejs Verza
Resolution: Fixed Votes: 0
Labels: SLA, configuration, view
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: GIF File error_message.gif     PNG File image-2022-08-15-14-42-25-956.png     PNG File image-2022-08-18-18-28-02-371.png     PNG File image-2022-08-18-18-29-15-072.png    
Team: Team A
Sprint: Sprint 90 (Jul 2022), Sprint 91 (Aug 2022)
Story Points: 0.5

 Description   

Problem description: The following SLA related issues are currently observed:
1 - Autocomplete is not working in the "Service" multiselect in Services => SLA report view.
2 - The format of the title of the Services => SLA report view is not condsistent with titles of all other views: the 2nd word in the title should not start with a capital letter, but in the above mentioned view the title is "SLA Report". Should be "SLA report"
3 - If an SLA was created via API with a defined effective date, and then this SLA was updated via frontend (even if no changes were made), then the effective date parameter gets rounded, which should not happen.

Steps to reproduce for point #3:

  1. Create an SLA using the following API:
    {
        "jsonrpc": "2.0",
        "method": "sla.create",
        "params": {
            "name": "TEST SLA",
            "period": 1,
            "slo": "11",
            "effective_date": "1651352400",
            "timezone": "Europe/Riga",
            "service_tags": [
                {
                    "tag": "t",
                    "value": "v"
                }
            ],
            "excluded_downtimes": [
                    {
                        "name": "EXCLUDED DOWNTIME",
                        "period_from": "1651352400",
                        "period_to": "1777582800"
                    }
            ],
            "schedule": [
                    {
                        "period_from": "0",
                        "period_to": "20000"
                    },
                    {
                        "period_from": "18800",
                        "period_to": "38800"
                    }
            ]
        },
        "auth": "42b89c7bde2ffd5086ec502a16af7a2f",
        "id": 1
    }
    
  1. Check the effective date in database, should be equal to "1651352400"
  2. Open the created SLA configuration in frontend
  3. Press update button without making any changes
  4. Check the value of the effective date in DB

Result: the value of the effective date was changed to 1651276800
Expected: the value of the effective date should not be changed



 Comments   
Comment by Andrejs Verza [ 2022 Jul 05 ]

Resolved in development branch feature/ZBX-21264-6.0

Comment by Andrejs Verza [ 2022 Aug 30 ]

Fixed in:

Generated at Wed Apr 16 11:15:57 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.