We are a content team and using Jira for bug tracking. We have different fields such as defect category (grammar, content, formatting, etc.), severity levels (showstopper, critical, major, etc) to quantify and categorize the issues. However, we are facing difficulty in pulling out defect reports. Now, we are exporting the data to Google Sheet to get the report. However, a few fields are missing. Is there an easy and foolproof way to do this so we get an accurate report?
One professional and reliable way to create native Excel reports (not CSV) for Jira bugs and defects is Better Excel Exporter for Jira Cloud.
The built-in templates export the fields you selected in the Issue Navigator or have on a Scrum or Kanban board. If the built-in templates are not enough, you can also customize your templates to get the results you want.
Here is a step-by-step guide to exporting a defects report from Jira to Excel.
(Please note that Better Excel Exporter is a paid and supported app and I'm part of the team developing it.)
Hello team,
I want to know how to create a custom report using date field and issue types in JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Anjana Lalitha
Welcome to the Atlassian Community!
Per your description, I understand you want to export your defects in a CSV file to properly create a report, however, some of the fields are not getting exported. Is that correct?
Can you please give us more details about the defects you are talking about? Is this a custom issue type you created or an issue type provided by a third-party app?
Basically, you can export all the fields of Jira issues to a CSV file by navigating to your issue navigator and click to export Excel CSV (All fields):
However, fields provided by third-party apps can have their own features and settings, so you would need to contact the support team of that app to know more details.
That being said, can you also let us know what kind of reports you would like to build?
Let us know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.