-
Type:
Story
-
Status: Closed
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Translations Management
-
Labels:
-
Epic/Theme:
-
Epic Link:
-
Sprint:LIMA | #02 | Sep03-Sep17
Value Statement
As a translator, I want to translate web content to all languages having the possibility to check the default content.
Functional Description
Permission definition tables that are related to assets that are possible to translate must have a "Translate" permission row.
A user with a translation role must be able to edit content in all languages but the default one.
Use Cases
- The user must be able to write content in the specified language due to translation permission in the role for a language
- The user must be able to check the content in the default language (we take as common base the default language although this could change in the future to translate from a translated language. An option could be the fallback language)
- The user must not be able to edit the default language content unless permissions allow.
Designs
Figma (translate permissions)
Figma Mockups (included 2 screens: with permissions / without permissions)
I've included an X circle icon to show the read only inputs, if it's not possible to apply the read only state, then use the disabled state
Interactions
- in the web content list, by clicking the actions menu will be possible to translate the content by opening it
- clicking the language button will open a dropdown menu with all the possible language to translate
- the users with permission will be able to translate the localizable content
- the users without permissions won't be able to translate, an info message will be shown at the top of the screen and all the inputs will be shown as read only (for text content) or disabled (for file type inputs)
Acceptance Criteria
Given a user with a translator role
When they access the actions available for web content
Then they see a "translate" action
Given a user with a translator role
When they click on the "translate" action
Then they will be directed to the web content editor
And they will be able to modify all languages but the default one
Dependencies
LPS-97861, LPS-97862, ------LPS-97869------
Test Scenarios
| ID | Test Priority | Test Scenarios | Covered by Backend (Unit/Integration)? | Test to add |
|---|---|---|---|---|
| 2.1 | 5 | The translator can see the "translate" action in assets when they are assigned the role | ||
| 2.2 | 5 | Clicking on the "translate" action redirects the user to the web content editor | ||
| 2.3 | 3 | All the possible language appear in dropdown menu after opening it | ||
| 2.4 | 5 | The translator can translate localizable contents to any possible language | ||
| 2.5 | 5 | The translator cannot modify the default language | ||
| 2.6 | 5 | A user cannot translate the content when they do not have translate permissions | ||
| 2.7 | 4 | An info message will be displayed when a non-translator accesses the web content editor | ||
| 2.8 | 4 | All the input fields in the web content editor are disabled for a non-translator | ||
| 2.9 | 5 | A user without edit permissions cannot see the "translate" option in the actions list |