-
Suggestion
-
Resolution: Unresolved
-
None
-
11
-
24
-
When Exporting a search or filter to CSV, including the "Key" field in the export will also include the Issue ID and the Parent ID.
Because the issue ID and Parent ID are not always needed or useful when using CSV exports for reporting purposes, and it can cause issues when lining up data in certain environments, it would be useful if the option to specify that it not be included in the CSV is included.
To this end, I would like to propose that a third export to CSV option be created to allow for explicit selection of which fields to export rather than rely on the current view as this is not immediately apparent to users what fields they have selected as it is common for them not to take an active role in selecting specific values.
- is related to
-
- Gathering Interest
- mentioned in
-
Page Loading...
[JRACLOUD-69860] Allow users to hide Issue ID and Parent ID fields while including issue key when exporting filter to CSV
+1 Please let us decide if those fields are included on the export list or not.
+1 Please let us decide if those fields are included on the export list or not
I suggest making all default id outputs such as Assignee Id and Creator Id be omittable as well. This customizability would really be helpful.
I agree, this is a pain for our company where we extract out and use for excel spreadsheets for demos and meetings as the reporting functionality in Jira is less than impressive without paying a small fortune for add-ons. As the data being exported sometimes has sub-tasks and sometimes does not, the parent ID may or may not be present, it makes formatting a nightmare.
The only way I have found around it is to always have KEY as the last item on your filter so it is always at the far right of exports and can be ignored, but it's hardly ideal.
having the key value is confusing for people to view in the filter page. it would be good if that could be excluded for a visual aspect.