Details
-
Suggestion
-
Resolution: Fixed
-
None
Description
Excel export should map each issue into a single spreadsheet row.
Currently, exporting as Excel produces a highly formatted spreadsheet where each JIRA issue gets spread out over many spreadsheet rows. JIRA merges cells to make it visually apparent that multiple spreadsheet rows are actually one JIRA issue. I suppose that works fine as far as it goes, though it is 100% useless to me:
Here are some examples of things that produce split rows:
- if the Description field contains line breaks, it gets split into several rows
- if issue is attributed with multiple components, it gets split into rows
The current approach breaks the most basic spreadsheet capability--sorting the issues. I don't export to Excel because I want to look at a pretty report. I export to Excel because I want to sort, characterize, and generally futz with the issues in ways that I cannot do (and don't expect to do) in JIRA. The current approach is absolutely useless to me. In fact, it adds negative value because I had to write an extensive VB macro to massage the default output into something usable.
Suggested behavior:
- Allow user the option of simple .csv or .xls export where each JIRA issue is mapped to a single spreadsheet row.
- For possibly compound fields like Component, concatenate mutliple values using user-selected intra-cell delimeter
Attachments
Issue Links
- duplicates
-
JRASERVER-7554 excel output can't be sorted when components is a column
- Closed
- was cloned as
-
JRASERVER-23323 Excel export should map each issue into a *single* spreadsheet row
- Closed