[ZBXNEXT-4142] API User group, not found field "Include subgroups" Created: 2017 Oct 03 Updated: 2021 Dec 24 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | API (A) |
| Affects Version/s: | 3.4.2 |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Minor |
| Reporter: | Pavel Kuznetsov | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 10 |
| Labels: | api | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Current Zabbix API object User group hasn't field |
| Comments |
| Comment by Dimitri Bellini [ 2019 Feb 26 ] |
|
Today i have discovered the same issue, some DevTeam could provide some information about this question? |
| Comment by Miotk Szymon [ 2019 May 24 ] |
|
Please align API with Web UI capabilities. |
| Comment by Dimitri Bellini [ 2020 Jul 20 ] |
|
Hi DevTeam, We still suffer of the lack of this option also for Zabbix 5.0, have you some idea on when this feature will alligned with API. Thanks so much |
| Comment by Miroslav [ 2021 Jun 09 ] |
|
Hi DevTeam, Has anyone investigated and have time plan to implement this functionality. Thank you.
|
| Comment by Werner Dijkerman [ 2021 Dec 24 ] |
|
Hi, One of the maintainers here from the https://github.com/ansible-collections/community.zabbix Ansible collection. When can we expect such an option? It is very critical for us to have this feature to be implemented as we are limited and thus an Ansible user should do complicated workarounds to get this done. Do understand where we live in 2021 (2022 soon) where Infrastructure as Code is very common and we don't manually do things in UI anymore. Thanks! |