Sidehistorik
| Tip |
|---|
This is a POC for using JIRA as a CMDB
An Issue is a "Configuration" item like a server, laptop, MySQL Database etc. |
| Info |
|---|
Why?
Well, most of the (seen from a ITIL Service Operation view) data is actually in JIRA, this is Incidents, Changes and Service Requests... Secondly, JIRA can be seen as a mere Form/workflow control system |
| Indholdsfortegnelse |
|---|
Architechture
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Data validity, quality and maintenance
JIRA has strict fields
JIRA has versioning on all field changes (history)
JIRA field can by updated by GUI and programmatically (CLI, RCP, SOAP)
Tabbed input:
Fields / Links to Configuration Items from/to other JIRA Issues - Hostname lookup on the Summary field works
an alternative to linking could be a (multi)select field on issues in JIRA - like Kepler DB Lookup - https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.databasecf
...
Daily summary: https://confluence.atlassian.com/display/JIRA/Receiving+a+Daily+Summary+of+Updated+Issues
Screenshots
Dashboard
...
Configuration Item (sample for a server)
Links to events / tasks / incidents:
Virtual Center Data:
Service / Support data:
Monitoreringdata:
¨
Workflow/Lifecycle
...
Does not work: issuetype=server and (Memory changed after startOfWeek("-1") before startOfWeek())"
Screenshots
...
Tests
Updating field(s) with no changes:
...