I am looking for the database table that stores custom field data for an issue.
not for update purpose; for understanding how it can be linked to an issue and where it is stored. I am going through the customfield, customfieldvalue tables but not able to connect them to the jiraissue table.
To expand on that... NEVER change a JIRA database while it's running. Even when it's not, you need to have a *total* understanding of what you're doing, and 99% of the cases I've run into where people use SQL writes simply don't. So they end up going back to a backup. Or worse.
I would argue that a lot. For 8 years i have replaced what should have been enterprise features with SQL hacks. Most hacks have been done with the server shut down, but some things i have done on the fly, with the application-server running (removal of last used agile-boards for instance). The biggest hacks i have done done so far did 1.9million updates ranging 44 tables in confluence, with the server being started up after the changes without issues. Binaya is specifically mentioning not doing updates, and in my book this is as safe as it gets. DISCLAIMER: Shit happens when you party hard, so knowing what you are doing is key to keeping the consistency of the database, and possibly to keeping your job. I warmly recommend dissecting a database dump to make sure all correlated data is changed when a table is updated, and also to ONLY do it on production after verifying that such a change has worked on a cloned environment. Failure to do so might render your knowledgebase/ticketing system beyond repair.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG