regards
I need to create a jira incidence putting data directly into database.
I managed to insert it, but I do not directly appear in the navigation panel. I have to edit the incidence and implement changes so as to show me in that panel.
Anybody would know which tables are to affect to create an incident correctly?
This is my version: 3.12.3-#302
Maybe it's not compatible with CLI :S https://studio.plugins.atlassian.com/wiki/display/JCLI/JIRA+Command+Line+Interface#JIRACommandLineInterface-Examples
¿This is correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is a very old version! However, createIssue is also an old capability and may work fine. If you look at v6 of that page's history it references your release for JCLI versions 1.0.0 through 1.5.0.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Niels is absolutely correct, you can NOT insert data directly into the database.
Jira caches data. both on disk and in memory, and that can overwrite anything you try to push into the database. If you have no other option than a database change, then this caching means that you cannot do it while Jira is running.
There's no sneaky work arounds or fixes for this - you *will* break your Jira if you amend data in the database while it is running. (There are some minor exceptions to this, but not many, and none that I know of that allow alteration/creation of issue data).
You can modify data while Jira is offline. But if you do, you must re-index the issue(s) affected somehow, and at the moment, the only ways to do that are to modify the issue somehow and trigger it or re-index the whole system.
If you do want to insert issues, you need to stop Jira, insert into the issue table, (possibly custom field values), the os_ tables for the workflow status, and the project and issue counters. Then start Jira and re-index it.
In other words, your "quickest solution" won't work - you *must* come up with something else.
A re-index will fix the search problems you have now, but there's other problems you may have created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i try to use the .net libraries and dont support https.
This is correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use any language that can talk to Jira via REST (or SOAP) if you want to do things externally. They should support https fine (the stuff I've written for it certainly does)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You don't want to bother. Cleaning the caches is not going to help you with inserting data in the database, because you would need to lock out all the users, clean the caches, run your SQL, prompt it to rebuild the caches, prompt it to re-index any issues affected and then let your users back in. You'll also need to write code, at the very least a plugin, to trigger the cache changes, and there may well be caches in Tomcat you need to think about too. Stopping Jira and starting it again after your SQL is complete is a far more simple way to do it.
You really do need to tell your project manager that they're utterly wrong about using SQL and that they have damaged your database by doing it. Then tell them that they need to invest in a little external code or scripting to do this properly.
I'd take a good look at Bob Swift's CLI, as it's really good for scripting (I know you're on an old version of Jira, there are older compatible versions of the CLI available). If that still doesn't meet the needs, then I know a SOAP interface is possible in .NET (That's your favoured technology if I've read correctly)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, database direct is a wrong way.
But i've a proyect manager jeje
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The safest way would be a restart. But I am not sure if there are any persistent caches that whould still be alive...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, there is a cache directory. There could be caches in the database, too. I personally would prefer not to work with JIRAs database directly ;-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i found this:
http://confluence.atlassian.com/pages/viewpage.action?pageId=223219172
this is correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jonatan,
I think you shouldn't alter JIRA's database directly for creating issues. This might cause invalid system states. It is better to use a remote API such as REST: https://developer.atlassian.com/display/JIRADEV/JIRA+RPC+Services
If you do a manual insert once, you might need a complete reindex. But this is nothing that should be done regularly...
Regards,
Niels
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.