[#JRA-8580] CSV Export from the issue navigator

JIRA

CSV Export from the issue navigator

Created: 20/Nov/05 04:38 PM Updated: 26/May/08 06:03 AM

Component/s:

Import / Export, Issue navigator

Affects Version/s:

3.4.1

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-9994 Extend CSV import to update already imported issues

~~JRA-10404~~ Make 'views' of content (single issue and search request) pluggable, and rewrite default implementations in velocity

This issue is related to:

~~JRA-10683~~ JIRA needs real CSV output

Participants:	A Gouaux, Anton Mazkovoi [Atlassian], Bettina Zucker, Henri Yandell, Mark Chaimungkalanont [Atlassian], Neal Applebaum, Nick Menere [Atlassian] and Steve Rigby
Since last comment:	21 weeks, 5 days ago
Support reference count:	5
Labels:

Description

« Hide

You should be able to do a CSV export from the issue navigator in a way that would be compatible with the CSV Imnporter. In that way, it'd then be possible to merge JIRA instances and also make exporting to reporting tools more seamless

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

A Gouaux - 20/Jan/06 11:33 AM

Any status on this?

[ Permlink | « Hide ]

Neal Applebaum - 20/Jan/06 04:45 PM

Just out of curiosity, why couldn't you Export to Excel and then save from Excel as a CSV file, and then import? I was thinking of doing that if I wanted to merge data from a test system to live.

[ Permlink | « Hide ]

A Gouaux - 20/Jan/06 04:55 PM

I don't know about others, but we've periodically seen some issues with
the Excel Export. As an example, just recently since upgrading to 3.4.2
one of our heaviest users has indicated that the Excel Export is
producing more rows than needed, wasting the upload process. So he had
to write something to strip out the blank rows. Seems like a CSV export
would eliminate all of that headache, and probably would be less
error-prone in general. I mean, it seems like a much simpler
protocol/mechanism to me, but what do I know.

[ Permlink | « Hide ]

Neal Applebaum - 21/Jan/06 09:24 AM

That (the extra rows) was a bug in the latest Excel export which was fixed for 3.4.3 in issue ~~JRA-8922~~. There's a patch (or 3) on that issue you could try. You can watch your user wince from all the effort made in fixing it as you install the patch

. And I've also customized my Excel to not generate those header and footer rows which span cells, not create the image at the beginning. I don't know who likes that

I also have a macro to remove hyperlinks from the generated Excel output. I was thinking that if you created a filter with just the fields you want for import, it should work. What am I missing?

[ Permlink | « Hide ]

Nick Menere [Atlassian] - 22/Jan/06 10:59 PM

Hi,

Neal does have some good points, but I can see for a few ocassions that an csv view would be better.
Unforetunately, we have not yet scheduled this issue.

I think our future goal for the Issue Navigator Views is to pluginfy it so that users can create their own views.

Cheers,
Nick

[ Permlink | « Hide ]

Bettina Zucker - 17/Jul/06 10:27 AM

Hello Neal,

I need either a clean csv export of my jira issues, or else
a customised excel which does exactly what your excel does:

1. not generate header and footer
2. not create the image

And additionally but most importantly:

3. not change the date-time and number formats!

I'm somewhat struggling with excel (2000) though.
How do I customize my excel so it is like yours?
I think if you give me some advice for 1. and 2. I then will
find a way to get also 3., but for now I'm quite clueless.

Cheers

Bettina Zucker

[ Permlink | « Hide ]

Neal Applebaum - 26/Jul/06 08:17 AM

Bettina - I'm still running 3.3.3 so I haven't investigated whether the changes to 3.4 and higher would be exactly the same, but it looks like it would be. The line numbers will be different
Here are my customizations:
In the file ... /secure/views/navigator/navigator-excel-current.jsp
Removed lines 50-69 (1 table tag, 3 tr tags) (lines 77-96 in 3.6)
and lines 99-105 (1 table tag) (lines 126-132 in 3.6)
Here's the first block to delete:

<table border="1">
<tr>
    <td bgcolor="<%= topBgColour %>" colspan="<%=colCount%>" height=30>
        <img src="<%= jiraLogo %>" width="<%= jiraLogoWidth %>" height="<%= jiraLogoHeight %>" border=0 alt="<%= AP.getDefaultBackedString(APKeys.JIRA_TITLE) %>">
    </td>
</tr>
<tr>
    <td bgcolor=ffffff colspan="<%=colCount%>">
        <a href="<webwork:property value="applicationProperties/string('jira.baseurl')" />"><font color=ffffff><webwork:property value="applicationProperties/string('jira.title')" /></font></a>
    </td>
</tr>
<tr>
    <td bgcolor=ffffff colspan="<%=colCount%>">
        <webwork:text name="'navigator.excel.results.displayissues'">
            <webwork:param name="'value0'"><b><webwork:property value="/searchResultList/size" /></b></webwork:param>
            <webwork:param name="'value1'"><b><webwork:property value="/outlookDate/formatDMYHMS(/outlookDate/now)"/></b></webwork:param>
        </webwork:text><br>
    </td>
</tr>
</table>

Here's the second block to delete:

<table border="1" >
<tr>
    <td bgcolor=dddddd colspan="<%=colCount%>"><font size=1>
        Generated at <%= new Date () %> <webwork:if test="remoteUser != null">by <webwork:property value="remoteUser/fullName" /></webwork:if> using JIRA <%= BuildUtils.getCurrentBuildNumber() %>.
    </font></td>
</tr>
</table>

I'm not sure what you're after with regards to date/time formats, but I just use Excel's format cells option to convert the date fields to the format I want (i.e. highlight a column and change the cell format for the column).

From my recollection, you don't need to restart JIRA for these changes to take effect (at least in my environment in standalone testing). Depending on your live environment, you might need to.

By the way, does anyone actually like that stuff in an Excel file?

I've also got customizations (in JIRA) to not export the "Tools" column from the Toolkit, and a macro (in Excel) to remove issue hyperlinks. Let me know if you want those too.

[ Permlink | « Hide ]

Bettina Zucker - 26/Jul/06 08:45 AM

Hello Neal,

it works! Thank you!
For the formats I also decided to use Excel format options.
I have a template .xlt file with my desired formats on a column name row, I then copy all the selected rows into it,
mark the column name row and copy the formats of all columns at once by sweeping the brush on the row's ruler.

Cheers
Bettina

[ Permlink | « Hide ]

Bettina Zucker - 19/Apr/07 09:32 AM

Hello,

I just found out that in jira 3.8 (don't know about 3.7, I upgraded from 3.6.2 directly to 3.8.1)
you have separate header and footer vm files containing the blocks above. The files are:

$JIRA_HOME/atlassian-jira/WEB-INF/classes/templates/plugins/searchrequestviews/searchrequest-excel-footer.vm

$JIRA_HOME/atlassian-jira/WEB-INF/classes/templates/plugins/searchrequestviews/searchrequest-excel-header.vm

Cheers

Bettina

[ Permlink | « Hide ]

Henri Yandell - 05/Nov/07 01:05 AM - edited

I've started work on a plugin for this:

http://outlet.googlecode.com/svn/trunk/jira-csv-view/

My current problem is figuring out how to turn the layout keyword of something like 'issuekey', into an issue.getIssue() or an issue.getString("key").

[ Permlink | « Hide ]

Steve Rigby - 21/Feb/08 09:43 AM

Hi,

I see this issue is over two years old now - is there likely to be any update on this at all?
As an open source company we try to use open source products like Openoffice and NeoOffice, neither of which handle the Excel export of Jira.
Thanks!
Steve

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 21/Feb/08 11:25 PM

Steve,

Due to a a large number of other popular feature requests were are not currently planning to implement this feature.

OpenOffice should be able to open JIRA's Excel export file. If you are having trouble with this please create a support request in our support system:
http://support.atlassian.com

Cheers,
Anton