For example, I can see a column, like severity, or platform in my JIRA website. But when I login the related JIRA Database in SQL Server2008 Management Studio, I can not see a table column, like severity or platform in any table, like jiraissue, etc.
Like with any software, you need to understand the architecture in order to understand the database.
JIRA is highly configurable so most of the data for issues will not be columns in the jiraissue table.
There are some hardcoded fields such as priority and environment that are in the jiraissue table but the rest would come from custom fields. For your particular columns, first find out what custom field type are being used for these items and then that can help find out how their storage is implemented.
Also, check out this doc http://confluence.atlassian.com/display/JIRA041/Database+Schema
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The SQL for JIRA add-on resolves the JIRA legacy database model complexity by providing a simplified data base model for JIRA. Only meaningful JIRA data for users are brought to the model, the rest of the JIRA internals are ignored.
So neither you nor other users at your organization have to access to the JIRA legacy database anymore. SQL for JIRA will save you from such wasting of time (and security risks).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.