Allow importing a single translation for web content with workflow disabled

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Translations Management
• Labels:
  • fc_20_06
• Epic/Theme:
  • Translation_Management
• Epic Link: lima-imp-exp-translation-content
• Sprint: LIMA | #19 | May26-Jun16, LIMA | #20 | Jun16-Jul07, LIMA | #21 | DEV | Jul07-Jul28

As a content admin

I want to be able to import a translation for a web content

so that I can easily add the work done by the translation agency

 

Acceptance criteria

 

Given a site with web content

When a user tries to import a translation

Then she can select an xliff file and import it 

 

Given a site with web content 

When a user publishes an imported translation

Then the translation is added to the web content

 

Given a site with web content 

When a user publishes an imported translation for an incorrect content

Then an error is shown explaining the situation

 

Given a site with web content 

When a user publishes an imported translation for a language no longer available

Then an error is shown explaining the situation

 

Given a site with web content 

When a user publishes an imported translation with a corrupted file

Then an error is shown explaining the situation

Design

Figma Mockup

Test Scenarios

ID	Test Priority	Test Scenarios	Covered by Backend (Unit/Integration)?	Test to add
16.06	5	User can select an xliff file when importing a translation for a web content	NO	Translations#ImportWebContentWithXliffFile Translations#ImportWebContent
16.07	5	User can import an xliff file to corresponding web content	YES	Translations#ImportWebContentWithXliffFile Translations#ImportWebContent
16.08	5	The translation is added to the web content once the user publishes the imported translation	YES	Translations#ImportWebContentWithXliffFile Translations#ImportWebContent
16.09	3	The system shows a success message indicating the import was published	NO	Translations#ImportWebContentWithXliffFile Translations#ImportWebContent
16.10	5	All the fields in the xliff file can be imported into the web content	YES	Translations#ImportWebContentWithXliffFile Translations#ImportWebContent
16.11	4	An error message displays when the translation file's ID doesn't match with the web content	YES	Manual
16.12	4	An error message displays when an imported translation using an unavailable language is published	YES	Manual
16.13	4	An error message displays when an imported translation with a corrupted file is published	YES	Manual
16.14	4	An error message displays when importing translation file has an incorrect encoding	YES	Manual
16.15	4	User can import the translation file after re-encoding it to UTF-8	NO	Manual