[ZBX-7969] service types not sorted in discovery action condition Created: 2014 Mar 20 Updated: 2017 May 30 Resolved: 2014 Mar 28 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Frontend (F) |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | 2.3.0 |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | richlv | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | actions, sorting, squashable | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
create a discovery action, add a new condition for service type - notice how service types are not sorted in the dropdown (they are in discovery configuration) |
| Comments |
| Comment by Pavels Jelisejevs (Inactive) [ 2014 Mar 20 ] |
|
Should be fixed together with |
| Comment by Eduards Samersovs (Inactive) [ 2014 Mar 28 ] |
|
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7969 |
| Comment by Pavels Jelisejevs (Inactive) [ 2014 Mar 28 ] |
|
(1) Discovery status must be sorted as well. Eduards Discussed and decided left as is. <richlv> please add the reasoning so we don't have to discuss it again 6 months later jelisejev Because now they are grouped by pairs Up - Down, Discovered - Lost. It looks better in this specific case. <richlv> thanks, CLOSED |
| Comment by Pavels Jelisejevs (Inactive) [ 2014 Mar 28 ] |
|
(2) Discovery services must be sorted automatically according their names returned by discovery_check_type2str(), not by hand. Eduards RESOLVED r.43851 jelisejev CLOSED. |
| Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 01 ] |
|
(3) I've made a minor code improvement in r43925, please review. Eduards CLOSED |
| Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 01 ] |
|
(4) No translatable strings changed. CLOSED. |
| Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 01 ] |
|
TESTED. Please review (3) before merging. |
| Comment by Eduards Samersovs (Inactive) [ 2014 Apr 01 ] |
|
Fixed in versions 2.3.0 (trunk) r.43927 |