@galads, if bugs are marked as "confirmed", does that already mean someone is working on it or when can one expect to see further action? What is your internal work-flow?

If I mark it as confirmed, means I am going to pick it up at some point when I filter according to priority.

Thanks for the feedback, @galads!

What does "some point" mean?
How is "priority" defined?

Sorry for the many questions but often customers are asking when to expect a fix.

Well, security issues have the highest priority. There are more than 1000 bugs still open and most are relevant and need to be sorted out. "some point" means provided I tested and reproduce the issue, then it will be fixed. And I test according to internal priority which, unfortunately, I cannot disclose here.

If you think a bug report is a priority, please assign it to me and I will pick it up from there.

@galads, can you assign a higher priority to this? I have heard from another customer missing these attribute fields.

This would be very helpful for us.
Axel Chudzik (BIOTRONIK)

@galads, this shouldn't be difficult to add and several people would benefit from it. Can we add this to the next sprint?

https://github.com/LimeSurvey/LimeSurvey/pull/2316

This «feature» can really broke browse response more an more …

I have survey with more than 60 token attribute, i really dislike to have it each time i browse response.
We need a "default column" to show before maybe ?

I think that there never is a perfect solution in this case. The common user (50%) does not use additional attributes. Others may use 1-3 attributes (40%). And only some very few (5%?) use > 10 attributes.
Are you should able to simply filter your view, see screenshot...

image.png (74,886 bytes)   

image.png (74,886 bytes)   

Yes but filter is not constant

It's why i put « We need a "default column" to show before maybe ? »

Allow to save default filter for each survey : globally (default by survey) + by user.

I think this is a bug introduced in my development. The description of this ticket talks about adding extra fields on the single response View but I believe that you're talking about these fields being available on the response browsing screen.

Let me review and I'll be back

@Mazi write «Single response overview» for me overview is on browse response :)

BUT : you're right : « See participant details including attribute details»

I create the Feature request about default global and by user

https://bugs.limesurvey.org/view.php?id=17995

@Mazi write «Single response overview» for me overview is on browse response :)

@Mazi the fields should be listed on the single response detailed view or on the general list of responses that you can browse?

BUT : you're right : « See participant details including attribute details»

(use mantis as IRC ;)

@gabrieljenik it should be "single response detailed view". Not sure if adding this to the "all responses" tabular overview makes sense.

This is just to confirm that the new fields for additional attributes only appear on the detailed response view.
These attributes don't appear on the browse responses screen. Having established that I believe got this ticket is ready for being tested. Thanks!

@gabrieljenik, what are the next steps to get the fix included at the next release?
I heard that "galads" is not available for further testing anymore?

@Mazi : maybe you can test it ?

Merged.

Ping to not forget to update the manual.

Does it have to be updated?

The PR said new feature. Dunno.

It is an enhancement to a current feature. Maybe a slight error on the commit message.
I believe no manual updates are needed.

This has already been merged.