3.8.7 "Spreadsheet" is broken

RT Users
1

The “Spreadsheet” link exports TSV which completely botches
the data values associated with our custom fields. The
Custom Field data appears in all the wrong columns.

Is this a known bug?

2

The “Spreadsheet” link exports TSV which completely botches
the data values associated with our custom fields. The
Custom Field data appears in all the wrong columns.

You may use as an alternative the extension
RT::Extension::SearchResults::XLS [1] which produce true Xls format and
so does not suffer from tsv limitations (encoding problems, tab
problems).

[1] - RT-Extension-SearchResults-XLS-0.09 - Add Excel format export to RT search results - metacpan.org

3

The “Spreadsheet” link exports TSV which completely botches
the data values associated with our custom fields. The
Custom Field data appears in all the wrong columns.

That’s not something I’ve heard reported. I do know we improved this
codepath for 3.8.8. Is there a chance you’re importing to your
spreadsheet as something other than TSV? (OpenOffice defaults to
importing tsv as tab, space, comma or semicolon delimited)

4

The “Spreadsheet” link exports TSV which completely botches
the data values associated with our custom fields. The
Custom Field data appears in all the wrong columns.

That’s not something I’ve heard reported. I do know we improved this
codepath for 3.8.8. Is there a chance you’re importing to your
spreadsheet as something other than TSV? (OpenOffice defaults to
importing tsv as tab, space, comma or semicolon delimited)

Using OO 3.2

Insert → Sheet from File → Results.tsv

Import dialog opens:

 Separator Options

 ( ) Fixed width

 (*) Separated by

     [x] Tab         [ ] Comma
     [ ] Semicolon   [ ] Space

= broken :frowning:

I’ll ask the original problem finder what app she was using.

5

Using OO 3.2
(*) Separated by

   [x] Tab         [ ] Comma
   [ ] Semicolon   [ ] Space

= broken :frowning:

I’ll ask the original problem finder what app she was using.

Does the data contain embedded tabs? If so, tab-delimited ain’t gonna work.

Is she sure she did TAB separated? Doing comma or space separated would jumble the data for sure.

Also look out for column widths. The spreadsheet can -look- like the data is jumbled when in fact it isn’t if the column widths aren’t uniform, which in some programs they often aren’t immediately upon an import like that. They -look- jumbled to me in OO as well, but then I go through and adjust column widths and its peachy.

Tom Lahti, SCMDBA, LPIC-1, CLA
BIT LLC
425-251-0833 x 117

6

Using OO 3.2
(*) Separated by

   [x] Tab         [ ] Comma
   [ ] Semicolon   [ ] Space

= broken :frowning:

I’ll ask the original problem finder what app she was using.

Does the data contain embedded tabs? If so, tab-delimited ain’t gonna work.

Is she sure she did TAB separated? Doing comma or space separated would jumble the data for sure.

Also look out for column widths. The spreadsheet can -look- like the data is jumbled when in fact it isn’t if the column widths aren’t uniform, which in some programs they often aren’t immediately upon an import like that. They -look- jumbled to me in OO as well, but then I go through and adjust column widths and its peachy.

Without a sample of what is wrong, or a better description of the bug,
I have to assume that the original reporter either wants to come up to
3.8.8 or apply 1f4fa271b9e9c78104257f729f3046f9c30694e0 which fixes a
bug where the column headers and column bodies might not be in sync.

-kevin

7

Jeff, et all,

I think it has been doing this for years. I just remember to change the Data
Type to “.xls” and all is well.

Kenn
LBNLOn Wed, Nov 3, 2010 at 1:16 PM, Kevin Falcone falcone@bestpractical.comwrote:

On Wed, Nov 03, 2010 at 01:05:25PM -0700, Tom Lahti wrote:

Using OO 3.2
(*) Separated by

   [x] Tab         [ ] Comma
   [ ] Semicolon   [ ] Space

= broken :frowning:

I’ll ask the original problem finder what app she was using.

Does the data contain embedded tabs? If so, tab-delimited ain’t gonna
work.

Is she sure she did TAB separated? Doing comma or space separated would
jumble the data for sure.

Also look out for column widths. The spreadsheet can -look- like the
data is jumbled when in fact it isn’t if the column widths aren’t uniform,
which in some programs they often aren’t immediately upon an import like
that. They -look- jumbled to me in OO as well, but then I go through and
adjust column widths and its peachy.

Without a sample of what is wrong, or a better description of the bug,
I have to assume that the original reporter either wants to come up to
3.8.8 or apply 1f4fa271b9e9c78104257f729f3046f9c30694e0 which fixes a
bug where the column headers and column bodies might not be in sync.

-kevin

8

Without a sample of what is wrong, or a better description of the bug,
I have to assume that the original reporter either wants to come up to
3.8.8 or apply 1f4fa271b9e9c78104257f729f3046f9c30694e0 which fixes a
bug where the column headers and column bodies might not be in sync.

-kevin

Thanks for the replies, all.

It was a bug in RT, fixed in 3.8.8.

This is fixed by changing the offending character in
share/html/Search/Results.tsv (the only difference
in that file between 3.8.7 and 3.8.8). I suspect
that’s what 1f4fa271b9e9c78104257f729f3046f9c30694e0
entails.