Quotas should be accessible for conditions and EM.
The quotas should be available via percentage and via counts.

See attached screenshot for a typical way to do it in other survey packages.
Another way to access quota during the interview is to get the status of quota questions. In the screenshot you can access the status (quota questions shown,answered and not answered as well).

The quota system is very basic. For example there is no quota on "not having clicked" an item (https://www.limesurvey.org/forum/german-forum/113472-pflichtantwort-bei-mehrfachauswahl-m%C3%B6glich)

Currently, this can only be solved via a workaround with a second hidden question.

by the way: I can't see the screenshot.

Other screenshots. No longer remember what I wanted to attach 2016.

Qualtrics.Quota01.JPG (55,163 bytes)   

Qualtrics.Quota01.JPG (55,163 bytes)   

Qualtrics.Quota02.JPG (51,054 bytes)   

Qualtrics.Quota02.JPG (51,054 bytes)   

Qualtrics.Quota03.JPG (50,875 bytes)   

Qualtrics.Quota03.JPG (50,875 bytes)   

Qualtrics.Quota04.JPG (56,658 bytes)   

Qualtrics.Quota04.JPG (56,658 bytes)   

It must not be related to quota but to "current response".

Sample :

• When you can come (you have 10 places for each day) : Monday, thirsday etc …
  OK : quota can be used, but clearly better with DAY_MONDAY.count <= 10

But for single choice need too DAY.choice.monday <=10 (for example)

See https://bugs.limesurvey.org/view.php?id=15246 sample plugin

Capture d’écran du 2019-09-07 11-22-07.png (21,355 bytes)   

Capture d’écran du 2019-09-07 11-22-07.png (21,355 bytes)   

With https://github.com/LimeSurvey/LimeSurvey/pull/1320

Potential Question Theme : hide (don't send HTML) with statCount function

We will focus this year on quotas and on improving ExpressionScript. We will create the bug reports/tickets accordingly when the time comes :)

Please don't close tickets WITHOUT PRESERVING the discussion, information etc.

Don't curse, Ollehar...

With statFunctions we already have something ready for some part :)

But : we don't have "answer filter" by Expression

Sorry for my language.

I don't understand, why this feature request was closed? Was that a mistake? Or what was the intention?

Perhaps it would help, when future architectural decision will be documented. To better understand what happend years ago ;-)

Status
What is the status, such as proposed, accepted, rejected, deprecated, superseded, etc.?

Context
What is the issue that we're seeing that is motivating this decision or change?

Decision
What is the change that we're proposing and/or doing?

Consequences
What becomes easier or more difficult to do because of this change?

https://github.com/joelparkerhenderson/architecture_decision_record/blob/master/adr_template_by_michael_nygard.md
https://adr.github.io/

I don't understand, why this feature request was closed? Was that a mistake? Or what was the intention?

Just some internal miscommunication, please ignore. It should be open and we'll continue to discuss it.

The description is

It should be possible to hide a question if a quota is met or not.

It can be done with simple quota currentky; Since we have countif exression function : we can close this issue ...

Or create a lot of child issue

1. Relevance for answers
   1. In radio list
   2. in dropdown ( https://gitlab.com/SondagesPro/QuestionSettingsType/unicityOnSingleChoice)
   3. On a single option on a single sub question in array question type
2. add a currentQuotaCount(quotaid ???) plugin
   1. The simplest part, but since i'm the only one working on core plugin, i'm unsure someone still interested by this way of simplify the core code ....
   2. Add a quota name to allow user to find the quota id .... and don't loos their good system when copy survey