View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 20415 | Bug reports | Menu system | public | 2026-02-02 19:16 | 2026-03-09 15:37 |
| Reporter | marcgold | Assigned To | |||
| Priority | high | Severity | partial_block | ||
| Status | new | Resolution | open | ||
| Product Version | 6.12.x | ||||
| Summary | 20415: Copy Survey Option Missing in 6.16.5 Update | ||||
| Description | On creating a new Survey from the top menu + the only option now is create. We used to have Copy which allowed you to copy an existing survey, give it a new name and Survey ID. This has disappeared in the latest release - This was not on the change log - so assume its an oversight. We can go to our template survey and copy this on the 3 dot menu - but this creates a survey with a new Name - so we end up taking extra clicks / steps to achieve the same funtionality. | ||||
| Steps To Reproduce | Try and create / copy survey. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 22 | ||||
| Complete LimeSurvey version number (& build) | 6.15.5 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | Any | ||||
| Database type & version | Any | ||||
| Server OS (if known) | Any | ||||
| Webserver software & version (if known) | Any | ||||
| PHP Version | 8.3 | ||||
I don't see this option; the only solution I can find is export lss/import lss. |
|
OK, on the survey listing ! Adding a new solution is a good idea |
|
|
@tibor.pacalat: We have seen many users complaining about the missing copy option. Can you please bring this back? |
|
|
@tibor.pacalat - Please bring this back up, the code changes I submitted in the private window mostly work, maybe they need to TLC from you guys, but they do solve our issue, but they do change the core functionality, so have to be redeployed each time we update, which we have held back on for now. So instead of updates rolling as you release, we have moved to quarterly, so we can manage this better. Please bring this feature back. |
|
|
Here, clearly : removing Copy and Import tabe in create surey are really a bad idea ! I really do not understand why LimeSurvey team make this kind of choice ! |
|
|
@Mazi and @marcgold I raised this with management some time ago, but the decision isn’t mine to make. I’ll follow up and try to get a clear, definitive answer for you. For now, this is how the feature was designed. |
|
|
@tibor.pacalat: I fully understand and of course I am not blaming you in any way! But removing a core UI element in a minor release change should NEVER be done this way. Literally every user copies surveys using that menu item. |
|
|
jeeez. just dealt with this issue. I agree with Mazi, that sort of change must never be in a minor release. I just downgraded gradually to last "working" vesrion to get people back to work and then found this report here. Yea its ok to have the descision to move the uround but this one is not the best way to do it. Lots of overhead work with this one. |
|
|
This is obviously causing some frustrations for multiple users as well as us. @TonisOrmisson downgrading is obviously one way and the way i did too, but then we lose out on the security patches so from my perspective not a trade off i really wanted. I looked at the possibility of a Plugin to do the same but there is No CopySurvey injection point to use. So created a little script to patch the files needed. I have tested on our system after the latest Comfort Update to 6.16.11+260303 Please have a look see if this is useful to others. |
|
You can do it via JS, surely, but it works until there is some other update that breaks the action ! Even in 7.X !: it's a bad idea to remove the usual function (both : import and copy) |
|
|
@tibor.pacalat, @c_schmitz: Can we please re-add this feature? There really are many, man people complaining about this decision and no one actually sees the benefit. |
|
|
@DenisChenu - I could not agree with you more. It is a really bad idea to remove normal function, especially in a sub release. I can see the logic in a major release if the new functionality improves the UI/UX. I have not looked at V7 yet, its too early for us. Note: 6.16.12 Security Release that drop today is fully functional with the patch in place, no reapplication needed. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-02-02 19:16 | marcgold | New Issue | |
| 2026-02-03 10:14 | DenisChenu | Note Added: 84162 | |
| 2026-02-03 10:14 | DenisChenu | Bug heat | 0 => 2 |
| 2026-02-03 10:18 | DenisChenu | Note Added: 84163 | |
| 2026-02-03 13:10 | marcgold | Bug heat | 2 => 4 |
| 2026-02-25 11:31 | Mazi | Note Added: 84306 | |
| 2026-02-25 11:31 | Mazi | Bug heat | 4 => 6 |
| 2026-02-25 11:40 | guest | Bug heat | 6 => 12 |
| 2026-02-25 11:45 | marcgold | Note Added: 84307 | |
| 2026-02-25 11:47 | DenisChenu | Note Added: 84308 | |
| 2026-02-25 12:00 | tibor.pacalat | Note Added: 84309 | |
| 2026-02-25 12:00 | tibor.pacalat | Bug heat | 12 => 14 |
| 2026-02-25 13:05 | Mazi | Note Added: 84310 | |
| 2026-02-26 16:08 | c_schmitz | Priority | none => high |
| 2026-03-06 15:21 | TonisOrmisson | Note Added: 84410 | |
| 2026-03-06 15:21 | TonisOrmisson | Bug heat | 14 => 16 |
| 2026-03-08 00:35 | marcgold | Note Added: 84416 | |
| 2026-03-09 08:00 | DenisChenu | Note Added: 84417 | |
| 2026-03-09 08:22 | Mazi | Note Added: 84418 | |
| 2026-03-09 10:55 | guest | Bug heat | 16 => 22 |
| 2026-03-09 15:37 | marcgold | Note Added: 84424 |