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

Allow marketers to select which vocabularies to show in the audit graph

    Details

      Description

      Motivation

      Content authors & marketers need to have insights about the volume of assets published under different categories in order to to evaluate the status of the content creation. The auditing of the already existing content is a fundamental tool, since it allows to know which content areas are already covered and to discover gaps in the content. The Content Audit graph will provide these insights in a glance, by representing visually two vocabularies' contents.

      With this feature, marketers and content authors can easily select which global vocabularies are to be featured in the graphic.

      Persona

      Content authors & marketers.

      Design

      https://www.figma.com/file/7OioAN94tAUQHPwYkNTOBn/LPS-115658-Allow-marketers-to-select-which-vocabularies-to-show-in-the-audit-graph?node-id=26%3A2646

      Technical Requirements

      • An option for selecting vocabularies will show in the content dashboard (table or audit areas)
      • User will choose from the list of global vocabularies available in the instance
      • User can choose a maximum of two vocabularies and a min of 0 (see LPS-116690)
      • If the user doesn't choose any vocabulary, then the audit graph will show the void state and the columns for vocabularies won't show in the table (see LPS-114911)
      • The two vocabularies selected will follow the ordering:
        • random /alphabetical in the table (not relevant)
        • For the content audit graph, the vocabulary with smaller number of categories will be featured in the Y axis, and the one with higher number of categories will be featured in the X axis  the category occupying the highest position in the "In Use" list will be featured in the X axis, and the second one will be featured in the Y axis (not developed in this story, but in LPS-116690)

      Acceptance Criteria

      • Given the content dashboard
      • When the user clicks on Configuration
      • Then a modal with two boxes (Available and In use) shows

      • Given the content dashboard
      • When the user clicks on Configuration
      • Then the "Available" box in the modal lists all existing Global Vocabularies

      – 

      • Given the content dashboard
      • When the user clicks on Configuration
      • Then Audience and Stage are the vocabularies selected (default status)

      Test Scenarios

      AC ID Test Strategy Test Scenarios Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd? (unit or integration) Poshi?
      01 Regression When the user clicks on Configuration, a modal is displayed with two boxes (Available and In use)  No  No  Yes
      02 Smoke When the user selects the option "Available", the modal lists all the existing Global Vocabularies  No  No  Yes
      03 Regression When the user clicks on Configuration, Audience and Stage are the vocabularies selected (default status)  No  No  Yes
      04 Sanity When the user clicks on the left or right arrows within Configuration and selects one or more vocabularies, the vocabularies go from Available to In use and vice versa  No  No  Yes
      05 Regression When the user clicks on the up and down arrows below the In Use box, the vocabularies are sorted alphabetically and vice versa  No  No  Yes

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              susana.vazquez Susana Vázquez
              Reporter:
              julia.molano Julia Molano
              Engineering Assignee:
              Susana Vázquez
              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