[dev.icinga.com #3391] add a different backend by using icinga2 api

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/3391

Created by mfriedrich on 2012-10-24 16:37:55 +00:00

Assignee: (none)
Status: Rejected (closed on 2014-07-19 12:17:10 +00:00)
Target Version: (none)
Last Update: 2014-12-08 09:27:46 +00:00 (in Redmine)

---

when the icinga 2 api becomes ready, classic ui should get an experimental backend change, in order to allow more than just compat. this is mainly for testdriving the api, and might not result into proper productive usage anyways (keep that in mind when expecting something).

---

Relations:

• relates #3391
• relates #3391
• precedes #3392

[icinga-migration]

Updated by mfriedrich on 2013-07-20 12:20:38 +00:00

• Target Version changed from 1.10 to 1.11

[icinga-migration]

Updated by mfriedrich on 2013-09-27 21:10:11 +00:00

• Target Version changed from 1.11 to 1.12

[icinga-migration]

Updated by mfriedrich on 2014-01-03 20:18:40 +00:00

• Priority changed from Normal to Low

[icinga-migration]

Updated by mfriedrich on 2014-07-19 12:17:10 +00:00

• Status changed from New to Rejected
• Target Version deleted 1.12

Wait for Icinga Web 2.

[icinga-migration]

Updated by mfriedrich on 2014-12-08 09:27:46 +00:00

• Project changed from 19 to Core, Classic UI, IDOUtils
• Category set to Classic UI