I would like to know if there is any way of retrieving the information from my saved filter using a query on a direct connection to mysql db.
If I want to generate the information and result is below 1000 rows, this is the process:
query - > search for issues -> export button -> choose "Excel (current fields)"
The information will automatically be saved on my local folder.
Currently, we have an issue on exporting the information from my save filter if the result set is beyond 1000 rows.
To be more clear, details are as follows:
JQL: project = projectxyz AND issuetype = "Customer Incident" AND created >= -52w
Information I would like to retrieve based on the JQL:
Please advise if there is a way to retrieve the same result from my save filter. Otherwise, kindly let me guide me on creating the sql-query to be able to get the data.
By the way. I'm using JIRA 6.1.1
I agree with Nic that the SQL will not necessarily be straightforward (although I believe that the resolution date actually is available in the jiraissue table).
However, if you want to increase the max limit of 1,000 rows in your export, this may save you from having to use SQL at all:
Your JQL is fine, you're limited in the Excel download because it's resource heavy and can overload your server if you use it with a large data set
You should be thinking about why you want thousands of records (a human simply can't process that much data, so you must be looking for summaries or data slices and a far better option that random downloads of already obsolete information is to do the reporting in Jira)
The SQL is complex - Key, issue type, created data, summary, status, and resolution are all on the main table jiraissue, but
to get first response and resolved, you'll need to read the history changeitem and changegroup to establish them, as they're not necessarily stored in the database at all
for custom field 1 and 2you need to read customfieldvalue and customfield
found-in and severity are odd. They are probably custom fields (in which case, see above). Unless you meant "priority" and/or "affects version", in which case, you can read jiraissue for the priority again, but you'll be mucking around with nodeassociation and versions to get affects version
Thank you very much for the detailed response. I will map the fields and hopefully everything can be retrieved easily. Currently, I've seen the table jiraissue for the other fields. I will check the history change item and change group for the other custom fields.
One thing, before 6.1, pkey is being ised for JIRA issue ID. Any advise on how it can be extracted for JIRA 6.1 and above?
I hope you will take some time to learn alittle SQL. It is a very important skill to have to understanding the various systems you might work with now and in the future. Copying code without a minimal understanding can be very dangerous to projects. i watch this
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs