How can I create a JIRA ticket with the issue ID directly to the sql database?

[Hines Trulock]

If the JIRA server service is down, is there a way to create a issue in the sql database and have an issue ID number ?  

[Nic Brough -Adaptavist-]

In theory, it is possible. 

But you need to understand exactly how Jira's database is structured, you'll have to do some calculations, and hit several tables, not just the core issue table.  After doing so, you will need to do a full locking re-index of your Jira after starting it back up before letting people use it.

In short, don't do it, it's a bloody nightmare.

You should add a queue function to your ticketing system - when it fails to raise a Jira issue, it keeps the record and tries again later.

[Dirk Ronsmans]

@Hines Trulock ,

I can't be sure as I am sure it wouldn't be a supported solution but dear lord I hope not! I can already think of all the inconsistencies that might happen as the application service itself is not running and you would basically be creating "ghost" tickets.

Wouldn't it make more sense to just keep track locally if your instance is down and inform the customers at a later point in time?

I'm curious to learn more about your use case as to why you would need to be able to do this?

[Hines Trulock]

We have a ticketing system that sends an email to the issue creator as well as to the service center.  When JIRA service is down, that ticket still comes through but without a ID #.  Looking for a way to still create the issue ID and show in the email.  

Basically some sort of offline queue that when JIRA comes back, it begins synching where it left off.