XLIFF files imported as draft translations

[svenseeberg]

Describe the Bug

After importing translations from XLIFF files the status of the translation is set to draft.

Steps to Reproduce

1. Open https://malte-test.tuerantuer.org/gumv/pages/de/
2. Select the Ukraine zip file and import
3. Translations are imported, but status is set to draft.

Expected Behavior

Pages should be visible.

Additional Information

The issue description is probably incomplete.

[timobrembeck]

This happens when no translation exists for the imported language or the latest translation is a draft.

[timobrembeck]

Should probably be implemented together with #1047

[svenseeberg]

That means the translation should inherit the status of the source at the time of export? 🤔 And we make it 2 bulk actions "Export published versions as XLIFF" vs "Export most current versions as XLIFF"?

[timobrembeck]

I'm not sure, I would prefer the solution to just export public versions and set the status to public for all imported versions again. For edge cases where drafts should be exported, we could suggest the workaround to publish them temporarily, export them as XLIFF and hide them again? But this is no real use case I think, since in most cases the translation should only happen when the content is finished and not a draft anymore.

[timobrembeck]

After clarification with the municipality team, the workflow should be exactly as it is at the moment, with the exception that the status should be inherited from the source language when no translation exists (in contrast to the fallback to DRAFT like it is at the moment).