[ZBXNEXT-597] Regexps should have a description field Created: 2011 Jan 01 Updated: 2015 May 22 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Change Request | Priority: | Major |
Reporter: | Oleksii Zagorskyi | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 3 |
Labels: | globalregexps, regexps, trivial, usability | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
Similarly to triggers that have comments and to item (planed it Why? This description can be displayed when view a list of all expression - there is enough free space. It would also be useful when deleting the expression to check into how many items and triggers it is used. For example, as is done recently to value mapping. Is at your decision. |
Comments |
Comment by richlv [ 2011 Jan 02 ] |
the idea about regexps having descriptions is a good one. |
Comment by Oleksii Zagorskyi [ 2011 Jan 02 ] |
Richlv, ok, idea about "checking where regexp is used" are registered as separate ZBXNEXT-598 |
Comment by Oleksii Zagorskyi [ 2014 Mar 19 ] |
One more point - if add the description field, then I'd suggest in frontend rename "Name" to for example "Alias". Because it's not just name which can be freely changed any time. It's a resource which used as reference in other places. For example we use this term ("Alias") in user's profile. |
Comment by richlv [ 2014 Mar 19 ] |
nonono. the "alias" in user properties must be renamed to "user name", it is really weird naming there. and for regexps we should not change name to alias either - long term we should have some proper validation, thus changing global regexp name would not be a breaking operation (maybe when all api is in server...) |
Comment by richlv [ 2015 May 22 ] |
description for :
|