Skip to content

Ability to group questions to break form into pages #357

Description

@ei8fdb

Feature request

Support form pagination

Rational

When designing large questionnaires/forms, using pagination (where the questionnaire is broken up into mulitple pages) helps the user by:

  • breaking the tasks into sub-tasks allowing them to focus on one-a small number of questions at a time
  • reducing the users cognitive load (less to intrepret)
  • reducing distractions (scrolling up and down the page)

UI

There's lots of ways of doing this. I can do some research into different approaches, but essentially it will:

  • allow the user to create pages
  • give it a title
  • possible a short description

It would also be really great if it supported conditional logic (that's another ticket - #358 or maybe #227)

There are many options on how to display this, but can help with designs if it helps.

Priority

High

As a user researcher who creates questionnaires having questions that can gather ranking data is very important - however I can understand this is a lot of design and a lot of work to implement. I'm happy to help out with this.

There's also a lot of ways to implement this so I think it requires time to discuss.

Thoughts?

Activity

  1. added
    0. Needs triagePending approval or rejection. This issue is pending approval.
    enhancementNew feature or request
    on May 6, 2020
  2. skjnldsv commented on May 6, 2020

    @skjnldsv
    Member
  3. added
    1. to developAccepted and waiting to be taken care of
    and removed
    0. Needs triagePending approval or rejection. This issue is pending approval.
    on May 6, 2020
  4. added this to the 2.2 milestone on May 6, 2020
  5. changed the title [-]Support form pagination[/-] [+]Ability to group questions to break form into pages[/+] on May 6, 2020
  6. modified the milestones: 2.2, 3.0 on May 6, 2020
  7. jancborchardt commented on May 6, 2020

    @jancborchardt
    Member

    Yes, we should absolutely support it. :)

    @ei8fdb can you show screenshots of how Google Forms does it?

  8. ei8fdb commented on May 6, 2020

    @ei8fdb
    Author

    @ei8fdb can you show screenshots of how Google Forms does it?

    Sure, I'll look at GoogForms and others. Goog's approach is OK, but it often trips me up.

  9. agentlibre commented on May 7, 2020

    @agentlibre

    It is probably next level, but in the same vein, I love this very smooth design from TypeForm if you haven't seen it yet:

    (specific example, I haven't found the generic feature yet, I'll edit my post if I do)

  10. jancborchardt commented on May 8, 2020

    @jancborchardt
    Member

    It is probably next level, but in the same vein, I love this very smooth design from TypeForm if you haven't seen it yet:

    Yeah, we analyzed that together with Google Forms – and to be honest the Typeform design, while looking nice, has several issues, like you have no idea how long a form actually is and it can feel a lot.
    So Google Forms’ simple default "1 page" is quite reassuring and easy, which is what we want to go for as well.

  11. removed this from the 3.0 milestone on Jun 12, 2020
  12. 2 remaining items

  13. jancborchardt commented on Jul 28, 2020

    @jancborchardt
    Member

    Yep, @jospoortvliet of course we should have the ability to group questions and break stuff into pages. :) I was specifically referring to Typeform’s design of "1 page per question" which is very specific and doesn’t give a good overview.

    Direct link of the research on conversion of multi-page forms: https://www.ventureharbour.com/multi-step-lead-forms-get-300-conversions/


    And some relevant reading on "wizards": https://www.nngroup.com/articles/wizards/, especially:

    Communicate a clear mental model of the process.
    Enforce a clear sequential order of the steps.
    Include buttons for navigating to the next and previous steps and label the steps descriptively
    Allow users to exit the wizard midway and save state. Allow them to resume the process at a later time.

    So we should require "page titles" which then show as a sequential navigation on top so people know where they are in the filling process.

  14. modified the milestones: 2.2, on Jan 21, 2021
  15. added
    usability testIssues which came up in the usability testing session by Ura Design
    on Jun 11, 2021
  16. RenataGegaj commented on Jan 21, 2022

    @RenataGegaj

    From the user testings: There was only one request for this feature(that participant had a background in research). A big +1 from my side as well for this. I often need it for my survey work.
    I quite like the SurveyMonkey approach on this. Basically, the user is presented with questions from a section in one screen but they become active on scroll. That way they don't compete for attention or cause confusion. There is also a progress bar at the bottom for visual presentation, supported by numbers, to reassure the user(example below). The only thing missing here is the section title.

    Screenshot 2022-01-21 at 15 10 07

  17. JOduMonT commented on May 19, 2022

    @JOduMonT

    I think I have a similar and compatible idea, I was thinking if it could be possible, via a cookie, or you know more than me, to save the status of an ongoing filling form. Which, in that case, could be when the person pass to the next question (I think LimeSurvey do that)

    My point is I have an intake form where I ask people to think about it and take their time (2-3days); of course they could leave the tab open and the computer on, but it would be awesome to generate a cookie with a URL, so they could refer to it when they want to continue where they left.

  18. modified the milestones: , 4.0, 4.1 on Nov 27, 2023
  19. modified the milestones: 4.1, Maybe someday on Jan 18, 2024
  20. foxhoundv commented on Mar 4, 2025

    @foxhoundv
  21. MFHagency commented on Oct 8, 2026

    @MFHagency
  22. Chartman123 commented on Oct 8, 2026

    @Chartman123
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions