I agree, my primary issue is how to set a survey to completed == "Y" even though the last groep/page has not yet been reached.

I started the discussion here to see if difficult roadblocks and/or additional ideas come up.

Whenever a new feature arises, we, as developers of surveys and software can imagine possibilities and can define many more additional features.

Making it possible to use the Expression Script so set {completed = "Y"} at a specific point would be great, but the implications may be unforeseen. Like: when completed = "Y" would it also be necessary to fill in a completion date?

Or are there more completion statusses necessary? Like submitted01, submitted02 ... submittedn

Or maybe an extra column: "status" where the developer can set arbitrary (self defined) statusses which can be used when filtering. "submitted" can be a "reserved status", only to be used by the core software. Maybe the column should be able to hold more statusses, like: ["submitted01", "submitted"]

For me this is brainstorming online; let's see if we can define a sweet spot which:
1 holds useful functionality
2 for which the development time/effort is overseeable
3 which can be explained to users (= survey developers)

You will than have to sum it all up and submit a feature request. Save your time and submit a feature request now. The concept of submitting bug and feature tickets late is not sustainable. The forum posts get wiped out over time. The forum helps raising interest for a ticket and help matching people. But opening a ticket early helps to find GUI/understanding issues too. Without tickets which gets closed directly because of an misunderstanding, no signal reaches the development team. It gets all covered by forum support and the root cause stays there forever.

@jelo: I thought of that too. But when I start a discussion here, I think I attract more "users" and I would like to add a feature request when I have enough views of users.

When I, based just on my own needs, add a feature request, I become part of a developers discussion, not of a users discussion. Users talk about the usage implications, developers talk about the technical implications. I think there is a slight difference between those two.

more "users" == tammo + jelo + me ?

One can always hope...

The missing vision/plan about LimeSurvey is the problem. The expectations of most stakeholders are unclear to me.

Without a vision about what kind of surveycreators LimeSurvey should please and help, you cannot neglect feature request upfront nor consider what are the most important feature requests to implement over the next two years. You end up with a flood of ideas and issues.

I would guess you will find only a few forumposts and bugtrackertickets with more than ten different people providing opinions and ideas.
You have many posts of 2-3 users with the same issue, which never reached the bugtracker and will get deleted in a few years.

The bugtracker/issue database is the repository with the highest chance of surviving anything and currently the only systematic approach against defragmentation of issues and ideas.