[MGNLCTS-175] Export in translations app only works for basic textfields Created: 13/Jun/23  Updated: 13/Sep/23

Status: Open
Project: Content Translation Support
Component/s: None
Affects Version/s: 2.5.9
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Robert Respondek Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: AuthorX improvements
Team: AuthorX

 Description   

Context

  • In the translations app: When you export the translations for a site, only basic textfields are considered
  • But most of our used fields are based on custom types
  • Thus for a test-page only ~600 of more than 3000 fields got into the exported excel
  • To fix this, we added a decorator for the list of types which are included and added our custom types here. But this was nasty and from now on whenever we add a new custom type we also have to add it in the decorator list. This might lead to missing value over time

Use Cases

  • Authors want to export whole sites as Excel-files, add all the translations in every line, and the import it again. So they don't have to click into every dialog and add translations there. That would be much slower.

Current Status

 

Proposal

  • The translation export/import should use fields of any type (including custom types) by default

Generated at Mon Feb 12 00:33:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.