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

As a marketer, I want to decide which languages I'm targeting when creating an experience

    Details

      Description

      Motivation

      So far we’ve kept as separated features experience variations and translation variations, but there are use cases where both are involved or one interferes in the other one. For example, when creating experiences targeting locales’ segments, multi-language feature becomes useless and fuzzy. So in this story we are proposing that the user will decide which locales s/he wants to translate into when creating an experience.

      Design

      https://www.figma.com/file/pfH8XUiCz7vmESxwBR6RCF/LPS-119080-Experiences-localization-and-translation?node-id=1%3A247 

      Technical Requirements

      • When creating a new experience, the user will select a segment to target (as currently s/he does) and then will select which languages s/he wants to translate it into from the list of all languages available in the portal. The default language will be selected by default, as it cannot be deselected. Languages will be alphabetically ordered, and the default will be in the first position.
        • When a locale is removed from the site:
          • Checks disappear
          • Flag for that locale disappear from UI
          • Translation will be saved in the database to be retrieved if needed.
        • When a new local is added, the new check will appear for all experiences, but it will be unchecked by default
        • When an existing or a new locale is set as default language:
          • default language check will be updated in the modal
          • The former default language will become a regular one and it will be selected for all existing experiences 
      • When clicking on the language selector (the one with the flag), only the selected locales will be displayed. Default language will be displayed in the last position of the dropdown.
      • User can edit the experience for selecting /deselecting any values.
      • In case of deselecting locales that already had their own translation, it won't be deleted from the database so it can be retrieved back if the locale is selected again.
      • Selected locales will be featured next to segment's name in the Experience summary
      • The locales selection will be transferred to the new one when copied as defined in LPS-121405 or sent to another one as in LPS-119077

      Acceptance Criteria

      • Given a content page
      • When the user hits "New Experience"
      • Then the new experience creation modal shows a list of deselected checkboxes with all current locales in the site

      • Given a site locales selection
      • When one locale is removed once it had a translation in a content page
      • Then the removed locale no longer appears neither in the checklist, nor in the flag dropdown, but if it's selected again as a site locale, then the existing translations are retrieved

      • Given a site locales selection
      • When one locale is added 
      • Then a new check for the new locale will appear for all experiences, but it will be unchecked by default

      • Given a site locales selection
      • When the default language is changed into a different one
      • Then the default locale will change in the checklist, and the former default language will become a regular one and it will be selected for all existing experiences 

      • Given an experience with n languages translated + the default one
      • When the default language is changed into a different one
      • Then the default language version shows the user's default language

      • Given the new experience creation modal
      • Then the default locale is selected by default and the Save button is always enabled

      • Given a new experience
      • When the user has selected some locales + the default one
      • Then the new experience shows those same locales in the translation switch button

      • Given any already existent experience
      • When the user hits the pencil icon (edit)
      • Then the experience creation modal shows and she can select/deselect whichever locales she wants

      • Given any already existent experience
      • Then the locales to which it can be translated into are shown in the experience row in the experiences selection modal

      • Given any already existent experience
      • When the user has translated it into any of the selected languages
      • Then if she deselects the locale and hits save, and she selects it again and hits save, the translation into that locale has not disappeared

      • Given any already existent experience
      • When the user duplicates it
      • Then the new experience has the same locales selected than the duplicated one

      • Given any existent experience with just some of the site locales selected
      • When a user with a not-selected locale arrives to the page
      • Then he's led to the default locale version of the experience

      • Given the experiences creation modal
      • Then available locales will be ordered alphabetically

      • Given an AB testing created from an experience with several languages selected
      • When the user creates a variant for the test
      • Then it is only possible to translate it into the selected languages of the current experience, and it is not allowed to edit them from the variant editing

      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 Low When a user clicks on "New Experience", the new experience creation modal shows a list of deselected checkboxes with all current locales in the site NO  NO  
      02 Medium When a new locale is added, a new check for the new locale will appear for all experiences NO  NO   
      03 Medium When a new locale is removed, the removed locale no longer appears neither in the checklist NO  NO   
      04 Low When a new locale is added, ir will appears unchecked by default NO  NO   
      05 Medium When a new locale is removed and it had a translation in a content page, the removed locale no longer appears neither in the checklist, nor in the flag dropdown, but if it's selected again as a site locale, then the existing translations are retrieved NO  NO   
      06 Low When the default language is changed into a different one, the default locale will change in the checklist and the former default language will become a regular one NO  NO   
      07 Medium When there is an experience with n languages translated + the default one and the default language is changed to a language that is not translated for this experience, ??????????????????      
      08 Medium When the default language is changed into a different one, it will be selected for all existing experiences NO NO   
      09 Low When a user clicks on "New Experience", the default locale is selected by default and the Save button is always enabled NO  NO   
      10 High When the user has selected some locales + the default one, the new experience shows those same locales in the translation switch button NO  NO   
      11 Low When the user has selected some locales + the default one and click "Cancel", the locales are not selected and unchecked for all the experiences NO  NO   
      12 Low When the user clicks on the pencil icon to edit a experience, the experience creation modal shows and she can select/deselect whichever locales she wants NO  NO   
      13 High When the user clicks on the pencil icon to edit a experience, selects some locales and clicks "Save", the edited experience shows those same locales in the translation switch button NO NO   
      14 Low When the user opens the experiences selection modal, the locales to which it can be translated into are shown for each experience NO  NO   
      15 Critical When the user opens the experiences selection modal and select a different locale for an experience, the experience is translated to that language NO  NO   
      16 High When the user duplicates an experience, the new experience has the same locales selected than the duplicated one NO  NO   
      17 High When there's an experience with some locales selected and a user with a not-selected locale lands on the page, he's led to the default locale version of the experience NO  NO   
      18 High When there's an experience with some locales selected and a user with a selected locale lands on the page, he's led to the matching locale version of the experience NO  NO   
      19 Medium If a user that has translated an experience into any of the selected languages deselects the locale, clicks on Save and select it again and clicks on Save, the translation into that locale has not disappeared NO  NO   
      19 Medium If a user that has translated an experience into any of the selected languages deselects the locale, clicks on Save and select it again and clicks on Save, the translation into that locale has not disappeared NO  NO   
      20 Low When a user clicks on "New Experience", the available locales will be ordered alphabetically      
      21 Medium When there is an AB testing created from an experience with several languages selected and the user creates a variant for the test, it is only possible to translate it into the selected languages of the current experience      
      22 Medium When there is an AB testing created from an experience with several languages selected and the user creates a variant for the test, it is not allowed to edit them from the variant editing      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              support-qa Support QA
              Reporter:
              julia.molano Julia Molano
              Engineering Assignee:
              Cristina Gonzalez
              Recent user:
              Carlos Brichete Báez
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:

                  Packages

                  Version Package
                  Master