JIRA as a CMDB

[B_ Normann P_ Nielsen]

I am looking into using JIRA as a small CMDB. My key desire is (for now) to:

1. Create a Project called CMDB

2. Not use the PROJECTKEY-NUMBER as the issue key, but a item name like a server called server1.sub.domain.dk

3. Find another solution to asure uniqueeness / lookup / link capabilities...

Is part 2 possible is any way?

[B_ Normann P_ Nielsen · Accepted solution]

Well, this seems not possible, and changing the key in "jiraissues" and reindexing is not working - just tested it on a development box.

So I will proceed with a CMDB project and a normal key - the Summary will be the FDQN of the server.

[Jobin Kuruvilla [Adaptavist]]

I am not sure what is CMDB but part 2 is difficult to achive without massive changes in the JIRA core code. I wouldn't recommend it because of the nightmare an upgrade can cause if you do so much changes.

It is not just JIRA. Integrations like Confluence, Fisheye etc and maybe few plugins also use that pattern to find JIRA issue keys.

[B_ Normann P_ Nielsen]

I am aware of that, but I can live with most problems, as I might use a standalone JIRA as the CMDB.

But thanks for the input :-)