To query the Exalate database for Jira on-premise and retrieve the specified error list information, you’ll need to write a SQL query. However, you should first ensure that you have the necessary permissions and access to the database.
Here’s an example SQL query that might help you retrieve the required information:
local_issue_id, remote_issue_id: Retrieve the local and remote issue IDs.
connection_name: Retrieve the name of the connection.
description: Retrieve the description of the error.
root_cause_details, root_cause_detail_text, root_cause_error_type_name: Retrieve details related to the root cause of the error.
creation_time: Retrieve when the error was created.
Make sure to adapt the table name exalate_errors and column names if they are different in your actual database schema. Also, ensure that the necessary SQL query permissions are in place to run this query on your Exalate for Jira database.
For more specific guidance or further customization, you may want to consult official Exalate documentation or reach out to your database administrator.
If you have any more questions or need further assistance, feel free to ask!
Found 0 results for 'database schema Jira on premise category:Exalate for Jira On Premise status:public'
Search
Found 1 result for 'database schema Jira on premise status:public'
I found a topic that might help you with querying the Exalate database for Jira on-premise. You can read more details in this post.
Please check it out for more specific guidance or customization based on the actual database schema and table structures. If you still face issues or have more questions, feel free to ask!
I apologize for the inconvenience. It seems there was an error with the link.
To query a specific Exalate database schema, such as Jira on-premise, the best course of action would be to consult the product documentation or reach out to Exalate support for the most accurate and detailed instructions. I recommend contacting your database administrator or Exalate support to obtain the exact database schema and table names used in your local setup.
If you need more assistance, you can also try the AIDA Chat bot available at AIDA Chat.