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

As a Form Admin, I want to check a summary of responses for my color field question

    Details

      Description

      As a Form Admin , I want to check a summary of responses for my color field question

      Design Deliverables

      Mockups
      Component

      Context

      One of the main purposes for a Form is to make Surveys and that's one of the main gaps that Liferay Forms has. During the product's life, we saw many users deciding to use Google Forms or some other Form Tool instead of Liferay Forms because they needed a Form answers summary report and didn't have one. Now we are trying to fix that by providing a brand new Answers Reports capability in Liferay Forms.

      In this Story's scope, users should be able to:

      1. Check the number of total answers that my Color field type had;
      2. Check a list with all the entries submitted for the Color field.

      Acceptance Criteria

      1- Given that a Form Admin created a Form with a Color Field Type and published;
      when one or more Form Submitter has already submitted answers to the Color Field,
      then the Form Admin should be able to check the Form Report and identify how many answers the Field had.

      2- Given that a Form Admin created a Form with a Color Field Type and published;
      when the Form already had submissions, but none of them has answered the Field,
      then the Field card should still be displayed in the Form Report, but with a "No Responses yet" status.

      3- Given that a Form Admin created a Form with a Color Field Type and published;
      when one or more Form Submitter has already submitted answers to the Color Field,
      then the Form Admin should be able to check the Form Report and see a list with all entries of the Color Field.

      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

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              Assignee:
              cleyton.magalhaes Cleyton Magalhaes (Inactive)
              Reporter:
              felipe.pires Felipe Pires (Inactive)
              Engineering Assignee:
              Marcos Martins
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master