View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 20713 | Bug reports | Other | public | 2026-09-21 12:09 | 2026-10-29 17:44 |
| Reporter | DenisChenu | Assigned To | c_schmitz | ||
| Priority | none | Severity | minor | ||
| Status | closed | Resolution | fixed | ||
| Product Version | 7.0.x | ||||
| Summary | 20713: Export ranking response as full answer export only code | ||||
| Description | When exporting ranking response and set Full answer : have only code | ||||
| Steps To Reproduce | Steps to reproduceImport the included survey Expected resultGet the full answers Actual resultGet the list of code | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Bug heat | 20 | ||||
| Complete LimeSurvey version number (& build) | 7.1.2 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | not relevant | ||||
| Database type & version | not relevant | ||||
| Server OS (if known) | not relevant | ||||
| Webserver software & version (if known) | not relevant | ||||
| PHP Version | not relevant | ||||
| Git branch / Pull Request URL | https://github.com/LimeSurvey/LimeSurvey/pull/5335 | ||||
|
I am diving in deeper here - I think it should still export them as seperate fields as before, not as one field. |
|
|
20714: Ranking questions export is not user-friendly https://bugs.limesurvey.org/view.php?id=20714 But see the feature : There are no good ways to export rankling questions, I worked in a Marketing Company years ago where the export of ranking questions used only one column (like today) About export system , maybe we need to review some "What we need to have a Question Type in plugin/theme" : add a "How I export the data" is needed in my opinion, but hard to offer with a theme (no PHP function) |
|
|
We use LimeSurvey in a nonprofit educational setting and have been very happy with it overall, but this latest change really bit us hard. We have a number of teachers who rely on the export of ranking questions with full question text instead of code (as it was in previous versions). We even built Excel macros to help process the old outputs for them and make them more usable. That is all broken now and we're dealing with unhappy teachers and complaints. They only use the system a handful of times a year but it's for tasks that are essential to running their classes. If we could just go back to the old way exporting question text for ranking columns, it would make a huge difference. At least then the Excel files we built to process that data would work again. Thanks for all the work you and the other developers and contributors do. |
|
|
Edit: I mean that we rely on export of ranking questions with full RESPONSE text instead of code (as it was in previous versions). |
|
|
Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=40917 |
|
|
Fixed in Release 7.7.0+261020 |
|
|
LimeSurvey: master 913dcc71 2026-10-19 11:28 Committer: GitHub Details Diff |
Fixed issue 20713: Ranking question answers exported as codes instead of full text (05335) |
Affected Issues 20713 |
|
| mod - application/helpers/admin/export/SurveyDao.php | Diff File | ||
| mod - application/helpers/admin/export/SurveyObj.php | Diff File | ||
| mod - application/helpers/admin/export/Writer.php | Diff File | ||
| mod - application/helpers/admin/exportresults_helper.php | Diff File | ||
| mod - application/libraries/Api/Command/V1/Transformer/Output/TransformerOutputSurveyResponses.php | Diff File | ||
| mod - application/models/Question.php | Diff File | ||
| mod - application/models/services/ExportSurveyResultsService.php | Diff File | ||
| mod - application/models/services/SurveyAnswerCache.php | Diff File | ||
| mod - tests/TestBaseClass.php | Diff File | ||
| add - tests/unit/helpers/admin/export/RankingExportTest.php | Diff File | ||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-09-21 12:09 | DenisChenu | New Issue | |
| 2026-09-21 12:09 | DenisChenu | File Added: survey_archive_Ranking.lsa | |
| 2026-09-21 12:13 | DenisChenu | Relationship added | related to 20572 |
| 2026-09-21 14:57 | c_schmitz | Assigned To | => c_schmitz |
| 2026-09-21 14:57 | c_schmitz | Status | new => assigned |
| 2026-09-21 14:58 | c_schmitz | Status | assigned => ready for code review |
| 2026-09-21 14:58 | c_schmitz | Git branch / Pull Request URL | N/A => https://github.com/LimeSurvey/LimeSurvey/pull/5335 |
| 2026-09-21 19:38 | c_schmitz | Status | ready for code review => assigned |
| 2026-09-21 22:23 | c_schmitz | Note Added: 85914 | |
| 2026-09-21 22:23 | c_schmitz | Bug heat | 0 => 2 |
| 2026-09-22 08:26 | DenisChenu | Note Added: 85916 | |
| 2026-09-22 08:26 | DenisChenu | Bug heat | 2 => 4 |
| 2026-10-16 19:06 | guest | Bug heat | 4 => 10 |
| 2026-10-16 19:08 | lsrvdec2021 | Note Added: 86504 | |
| 2026-10-16 19:08 | lsrvdec2021 | Bug heat | 10 => 12 |
| 2026-10-16 19:10 | lsrvdec2021 | Note Added: 86505 | |
| 2026-10-17 09:20 | c_schmitz | Status | assigned => ready for code review |
| 2026-10-19 11:28 | c_schmitz | Changeset attached | => LimeSurvey master 913dcc71 |
| 2026-10-19 11:28 | c_schmitz | Note Added: 86541 | |
| 2026-10-19 11:28 | c_schmitz | Status | ready for code review => resolved |
| 2026-10-19 11:28 | c_schmitz | Resolution | open => fixed |
| 2026-10-20 17:06 | LimeBot | Note Added: 86574 | |
| 2026-10-20 17:06 | LimeBot | Status | resolved => closed |
| 2026-10-20 17:06 | LimeBot | Bug heat | 12 => 14 |
| 2026-10-29 17:44 | c_schmitz | Relationship added | has duplicate 20714 |
| 2026-10-29 17:44 | c_schmitz | Bug heat | 14 => 20 |