View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
09460Bug reportsCentral participant databasepublic2015-06-18 10:46
Reporterduvemyster Assigned Totpartner  
PrioritynormalSeverityminor 
Status closedResolutionsuspended 
Product Version2.05+ 
Summary09460: A participant attribute dropped under the wrong existing token attribute cannot be corrected midstream without staring over
Description

When mapping participant attributes to an existing token attribute via drag-and-drop, if you accidentally drop a participant attribute below the wrong existing token attribute and then realize it, then only way to recover seems to be to return back to the previous screen and start over again at "add participants to a survey"(or am I missing something?).

Steps To Reproduce
  1. Start from a CPDb with participant attributes
  2. Add participants to a survey with existing token attributes
  3. Drag a participant attribute under an existing token attribute and let go.
  4. Now try to move this same participant attribute to a different token attribute instead. (It looks like it is going to work, but when it is let go it then jumps back to the original place where it was dropped.)
Additional Information

Similar to this, it is also easy to accidentally drop more than one participant attribute under a single existing token attribute. Unless I am missing something, it also seems that the only way to recover from this when it occurs is to return back to the previous screen and start over again at "add participants to a survey".

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)141229
I will donate to the project if issue is resolvedNo
BrowserFirefox 35.0
Database type & versionMySQL 5.1
Server OS (if known)Linux
Webserver software & version (if known)Apache/2.2
PHP Version5.4.10

Users monitoring this issue

There are no users monitoring this issue.

Activities

sammousa

sammousa

2015-06-15 10:36

reporter   ~32356

Last edited: 2015-06-15 10:36

In 3.0 this interface has been rebuilt.
@tpartner: Contact me if you'd like the info for testing if this bug still exists there.

Since there is a workaround I suggest not fixing this for 2.x.

tpartner

tpartner

2015-06-15 12:40

partner   ~32362

@sammousa, I agree, given the imminent release of 3.0, it's probably not worth fixing.

c_schmitz

c_schmitz

2015-06-18 10:46

administrator   ~32417

Version 2.06+ Build 150618 released

Issue History

Date Modified Username Field Change
2015-01-15 18:57 duvemyster New Issue
2015-05-22 14:00 tpartner Assigned To => tpartner
2015-05-22 14:00 tpartner Status new => assigned
2015-06-15 10:36 sammousa Note Added: 32356
2015-06-15 10:36 sammousa Status assigned => feedback
2015-06-15 10:36 sammousa Note Edited: 32356
2015-06-15 12:40 tpartner Note Added: 32362
2015-06-15 15:43 c_schmitz Status feedback => resolved
2015-06-15 15:43 c_schmitz Fixed in Version => 3.0
2015-06-15 15:43 c_schmitz Resolution open => suspended
2015-06-18 10:46 c_schmitz Note Added: 32417
2015-06-18 10:46 c_schmitz Status resolved => closed