Something went wrong while setting issue due date.
DNS postLdapSave should lock the object modified
Closed
DNS postLdapSave should lock the object modified
/* FIXME - We should lock the zone object and check if we don’t erase changes */
DNS postLdapSave should lock the object modified
/* FIXME - We should lock the zone object and check if we don’t erase changes */
changed the description
added 5m of time spent at 2019-06-04
changed due date to June 04, 2019
I guess you meant #5340 (closed) , but it is not a duplicate this one is about DNS, not DHCP.
added plugin-dns label
removed plugin-dhcp label
added 5m of time spent at 2019-06-04
removed due date
changed due date to June 05, 2019
removed due date
changed due date to June 12, 2019
added 5m of time spent at 2019-06-04
mentioned in commit 82ef9abe
added 2h of time spent at 2019-06-20