[#JRA-8900] When issues are exported to Excel, only the first 80 characters of a custom field are exported

JIRA

When issues are exported to Excel, only the first 80 characters of a custom field are exported

Created: 28/Dec/05 08:07 AM Updated: 26/Nov/06 11:16 PM

Component/s:

Custom Fields, Web interface

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Windows 2003

Issue Links:

Duplicate

This issue duplicates:

~~JRA-8218~~ Inconsistency between displaying free text custom field and description in issue navigator results

Reference

This issue relates to:

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

Participants:	=Neal Applebaum, Christopher Woodill, Jeff Turner [Atlassian] and Mark Chaimungkalanont [Atlassian]
Since last comment:	2 years, 40 weeks, 3 days ago
Resolution Date:	10/Jun/06 01:06 AM
Labels:

Description

« Hide

We've created a custom field called "Elements Affected" which is a free-text field of unlimited length. When the issues are exported to Excel, only the first 80 characters of this field are included. This is a critical problem for us in that this field has several hundred characters in it and we need to export this field to Excel on a routine basis.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

=Neal Applebaum added a comment - 28/Dec/05 09:03 AM

What version are you on? I reported this a while back and it was fixed - in 3.3 I believe. For my issue (~~JRA-7107~~) Dylan from Atlassian also had a workaround to fix the source code... but I can't find it now. Anyway, the fix would depend on the version you're on. It would help if you update the issue with your version.

[ Permlink | « Hide ]

Christopher Woodill added a comment - 28/Dec/05 09:14 AM

Version is 3.4.1.

[ Permlink | « Hide ]

=Neal Applebaum added a comment - 28/Dec/05 09:40 AM

Then it sounds like they've re-introduced a bug in 3.4. See issue ~~JRA-8198~~ and ~~JRA-8218~~ where they gave some code fix workarounds. Since each of those issues had a different solution, maybe both were implemented, causing 3.4.1 to break as well.

My comment in ~~JRA-8198~~ was:
Note that Nick's solution will only work if you also modify view-basictext.vm. Since I followed the instructions in ~~JRA-8218~~ and it works for me in the issue navigator view as well, why don't you give that a try.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 28/Dec/05 09:48 PM

Christopher,

It looks okay to me in 3.4.2 (here on jira.atlassian.com). For example, do an 'all fields' excel view on:

http://jira.atlassian.com/secure/QuickSearch.jspa?searchString=TST%20%22Large%20CF%20value%22

and you'll see a custom field with 100 characters:

<td class="nav customfield_10170"> this is a looooooooooooooooooooooooooooooooooooooooooooooooooooooooong text field of 100 characters
</td>

Perhaps your spreadsheet is truncating the display of the value?

[ Permlink | « Hide ]

Christopher Woodill added a comment - 03/Jan/06 08:20 AM

This works for me. Maybe the bug was fixed in 3.4.2?

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 03/Jan/06 09:21 PM

Christopher,

This should've been something that was fixed in ~~JRA-8218~~, unless you have you own customized custom field types.

I'll close this issue as a duplicate and please reopen if you still find it an issue in 3.4.2

Cheers

Mark C