Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-109654

As a Form Admin, I want to see the number of responses that my Form has

    Details

    • Epic Link:
    • Sprint:
      Forms_7.3_21, Forms_7.3_22, Forms_7.3_23

      Description

      As a Form Admin, I want to see the number of responses that my Form has, so that I can have a clue of my Form's response rate

      Design Deliverable:

      Mockups

      Context

      Liferay Form has already the capacity to let users see the entries that were submitted on each Form created. However, this view entry capacity is not enough for some use cases. Mostly for Surveys use cases, when a user isn't looking for a detailed open data of each submission, but a quantitative of qualitative summary of all the answers.

      To solve the problem of this low-hanging fruit of our product, we need to provide a space where users can see and understand a summary of each question of the form, considering all entries.

      This Story is about solving one minor problem of this Forms Report epic, which is to understand how many answers a Form has. This way, users can understand how is the response rate of the Form and learn when they have gathered information enough.

      Acceptance Criteria

      1- Given a Form created in Liferay with one or more answers,
      when a users accesses Liferay Forms Portlet and acceses the Form,
      then the user must also have access to a tab with the entries information and summary.

      2- Given a Form created in Liferay with one or more answers,
      when a users accesses the "Entries" tab of the Form,
      then the user must be able to identify how many entries the Form has.

      3- Given a Form created in Liferay with one or more answers,
      when a users accesses the "Entries" tab of the Form,
      then the user must be able to identify how long was since the last entry submission in the Form.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Verify if the test labels were added;
      • Code with peer review completed;
      • Validated by QA, Product Designer and/or PM;
      • No critical bug related to Story scope (ex.: similar of FP4, FP5);
      • Make sure that all system documentation were updated (if necessary)
      • Make sure that it has the extensions points needed to allow GS and customers to customize the feature (if applicable)

        Attachments

          Activity

            People

            • Assignee:
              matheus.xavier Matheus Xavier
              Reporter:
              matheus.xavier Matheus Xavier
              Engineering Assignee:
              Matheus Xavier
              Recent user:
              Eduardo Zoby
              Participants of an Issue:
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Packages

                Version Package
                Master