Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-23323

Excel export should map each issue into a *single* spreadsheet row

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Excel export should map each issue into a single spreadsheet row.

      go to a Issue Navigator ticket view
      say this one
      http://jira.atlassian.com/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JRA+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide

      Export to Excel with the current columns

      You will note that it generating Merged Cells, so each single ticket is actually taking up 2 rows. This makes it impossible to sort.

      (I cloned this ticket, as it appears to have happened in the past)

            [JRASERVER-23323] Excel export should map each issue into a *single* spreadsheet row

            The workaround worked for us as well, and solved a major user complain without having to go through the entire installation, export, import process. Much thanks.

            Josh Weisman added a comment - The workaround worked for us as well, and solved a major user complain without having to go through the entire installation, export, import process. Much thanks.

            Owen Carter added a comment - - edited

            I have a workaround that fixes it in our install - edit the above file in the deployment directory, and wrap the last line, the one with the offending div, in a conditional (pulled from the content above it) to only output the DIV if the display is NOT Excel:

            Greg, you are a star! that worked as expected (after a Jira restart) thanks got me out of a real hole there..

            • we nearly stopped out Jira 3->4 rollout this weekend because of this. Now I can go ahead, phew...

            Owen Carter added a comment - - edited I have a workaround that fixes it in our install - edit the above file in the deployment directory, and wrap the last line, the one with the offending div, in a conditional (pulled from the content above it) to only output the DIV if the display is NOT Excel: Greg, you are a star! that worked as expected (after a Jira restart) thanks got me out of a real hole there.. we nearly stopped out Jira 3->4 rollout this weekend because of this. Now I can go ahead, phew...

            Hi,

            What is the eta for 4.2.2?

            Early January

            Cheers,
            Peter

            Peter Leschev added a comment - Hi, What is the eta for 4.2.2? Early January Cheers, Peter

            After some digging, I can narrow the problem down to a change in the XML used for the "Summary" navigator column specifically. Remove that column from your Issue Navigator display, and the Views > "Excel (current fields)" download looks right in Excel - one row per issue, no vertically merged cells.

            You are not outputting actual Excel binaries, but XML with the ".xls" file extension and Excel MIME type in the HTTP response headers and the Excel XML namespace in the content.

            That content looks like this for Summary column cells:

                                               <td class="nav summary"  ><p>
                            send email (without password) to new user even if it is from LDAP
                </p>
            <div class="ie7minWidth"></div>
            </td>
            

            Remove the DIV (which appears to be a hack for proper display inside IE7 only?), and the row is processed as expected by Excel, with no merged cells.

            I've not been able to adjust the CSS to have Excel process that cell as a single row without causing the whole row to consist of vertically merged cells.

            This HTML comes from WEB-INF/classes/templates/jira/issue/field/summary-columnview.vm in the JIRA WAR file or standalone document root.

            I have a workaround that fixes it in our install - edit the above file in the deployment directory, and wrap the last line, the one with the offending div, in a conditional (pulled from the content above it) to only output the DIV if the display is NOT Excel:

            OLD
            {{ <div class="ie7minWidth"></div>}}

            NEW

            #if ( ! ${displayParams.excel_view})
                <div class="ie7minWidth"></div>
            #end
            

            Greg Woolsey added a comment - After some digging, I can narrow the problem down to a change in the XML used for the "Summary" navigator column specifically. Remove that column from your Issue Navigator display, and the Views > "Excel (current fields)" download looks right in Excel - one row per issue, no vertically merged cells. You are not outputting actual Excel binaries, but XML with the ".xls" file extension and Excel MIME type in the HTTP response headers and the Excel XML namespace in the content. That content looks like this for Summary column cells: <td class="nav summary" ><p> send email (without password) to new user even if it is from LDAP </p> <div class="ie7minWidth"></div> </td> Remove the DIV (which appears to be a hack for proper display inside IE7 only?), and the row is processed as expected by Excel, with no merged cells. I've not been able to adjust the CSS to have Excel process that cell as a single row without causing the whole row to consist of vertically merged cells. This HTML comes from WEB-INF/classes/templates/jira/issue/field/summary-columnview.vm in the JIRA WAR file or standalone document root. I have a workaround that fixes it in our install - edit the above file in the deployment directory, and wrap the last line, the one with the offending div, in a conditional (pulled from the content above it) to only output the DIV if the display is NOT Excel: OLD {{ <div class="ie7minWidth"></div>}} NEW #if ( ! ${displayParams.excel_view}) <div class="ie7minWidth"></div> #end

            Ann Myers added a comment -

            Hello!

            What is the eta for 4.2.2?

            Thank you! (didn't see a fix version for it)

            Ann Myers added a comment - Hello! What is the eta for 4.2.2? Thank you! (didn't see a fix version for it)

            This will be fixed in JIRA 4.2.2

            Peter Leschev added a comment - This will be fixed in JIRA 4.2.2

            Marilyn Daum added a comment - - edited

            We have noticed this too, new with the 4.2.1 upgrade. In addition, column A is always prepended with the issue number, so instead of "Bug" it now reads "DOCS-198 Bug", which makes sorting extra challenging. I have worked around this by changing my default navigator to have an always-blank field in the first column.

            It's quite annoying, as I use Excel exports regularly. Please fix this soon!

            Marilyn Daum added a comment - - edited We have noticed this too, new with the 4.2.1 upgrade. In addition, column A is always prepended with the issue number, so instead of "Bug" it now reads "DOCS-198 Bug", which makes sorting extra challenging. I have worked around this by changing my default navigator to have an always-blank field in the first column. It's quite annoying, as I use Excel exports regularly. Please fix this soon!

              Unassigned Unassigned
              7225804bfb60 Ann Myers
              Votes:
              6 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: