Issue Summary

While exporting JQL search results to CSV/XML (but not HTML), the values for the "Story Points" custom field are appended with trailing '.0' even if this field has a whole number value.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Search for issues with the "Story Points" custom field (add "Story Points" to the search results if required). You could use JQL query similar to the below:

   project = "<project>" AND "Story Points" is not EMPTY ORDER BY key ASC
   

2. Export search results to CSV (All fields or Current fields) or XML
3. Review export results — the generated export file will have whole "Story Points" values appended with trailing '.0'
   

Here is how values are stored in Jira DB:

select jp.pkey, ji.issuenum, cf.cfname, cfv.stringvalue, cfv.numbervalue
from project jp, jiraissue ji, customfield cf, customfieldvalue cfv
where jp.id = ji.project
and cfv.issue = ji.id
and cf.id = cfv.customfield
and jp.pkey = 'SAM'
and cf.cfname = 'Story Points'
order by jp.pkey, ji.issuenum;

 pkey | issuenum |    cfname    | stringvalue | numbervalue
------+----------+--------------+-------------+-------------
 SAM  |        1 | Story Points |             |         2.5
 SAM  |        2 | Story Points |             |           2
 SAM  |        3 | Story Points |             |           5
 SAM  |        4 | Story Points |             |           5
 SAM  |        5 | Story Points |             |           1
 SAM  |        6 | Story Points |             |           1

Expected Results

From the user perspective, it is expected that "Story Points" values would be exported in the way they are stored in DB and represented in Jira UI.

Actual Results

The values for the "Story Points" custom field are appended with trailing '.0' even if this field has a whole number value.

Workaround

Currently, there is no known workaround for this behaviour (except the usage of HTML export which is not impacted by this issue). A workaround will be added here when available