Hey everyone,
I’m trying to pull data from JIRA into Snowflake using Matillion. I’ve got a JIRA token set up and I can see most of the tables, but I’m having trouble finding the form data.
Does anyone know which table contains the form information? Or is there a special way to access it?
I’ve attached a screenshot of the tables I can currently see, but the form data is nowhere to be found. Any tips or suggestions would be really helpful!
Thanks in advance for your help!
As someone who’s worked extensively with JIRA integrations, I can tell you that form data can be tricky to locate. Have you looked into the ‘issuelink’ table? It often contains relationships between issues, which might include form submissions. Another approach is to check the ‘changelog’ table - sometimes form data gets logged there as changes to the issue.
If those don’t pan out, you might need to dive into JIRA’s database schema more deeply. The ‘propertyentry’ table can sometimes hold custom data that doesn’t fit elsewhere. Lastly, don’t overlook the possibility that the form data might be stored as attachments. In that case, you’d want to investigate the ‘fileattachment’ table.
Remember, JIRA’s data structure can vary based on your specific setup and plugins. If all else fails, reaching out to your JIRA admin or Atlassian support might give you insights specific to your instance.
hey neo, have u checked the ‘issue’ table? sometimes form data is stored there as custom fields. if not, try querying the ‘customfield’ table - it might contain what ur looking for. also, double-check ur JIRA permissions to ensure u have access to all necessary data. good luck!
I encountered a similar issue when integrating JIRA with Snowflake. The form data isn’t always straightforward to locate. Have you explored the ‘customfield_value’ table? It often contains the actual values for custom fields, including form data. Additionally, the ‘customfield’ table might provide metadata about these fields. If you’re still stuck, consider using JIRA’s REST API directly through Matillion’s API component. This approach allows more granular control over the data you’re extracting, potentially circumventing limitations in the standard table structure. Remember to thoroughly document any custom extraction methods for future reference.