Change Details

When users have not been working on a translation for a while, a notification can help them to (a) continue the work, or (b) decide to publish the current content (avoid this knowledge to be lost). Considerations: - We want to notify about drafts without activity since last month (only sending one notification mentioning all pending) -- In the translation list we want to add a label marking those drafts. - We want to consider only drafts for which the corresponding article has not been published. -- We want to research how many drafts have an article that existed before the draft (this was a test by the user for CX: I'll try to translate "Paris"), after the draft (may have problems publishing), or went back to draft after publishing (users edited something). - This requires a background job to trigger the notifications.

When users have not been working on a translation for a while, a notification can help them to (a) continue the work, or (b) decide to publish the current content (avoid this knowledge to be lost). This is also useful as a warning for old drafts being automatically deleted (T183890), and preventing the issues of trying to continue a translation for which the original article has changed significatively. # Proposed solution Send a notifications for translations that were started 3 months ago and have not been published by the user. If there are several translations in such situation, the notifications will be grouped into a bundle. These notifications are illustrated below: {F12261110, size=full} - Text copy: "Your started translating <page-name> some months ago. Consider publishing it before it gets automatically discarded after a year." - Main action (opening the notification): leads to the Translation editor for the translation. - Secondary action: “Your translations” leads to the Translations dashboard showing the in-progress view. **Bundled version** {F12261125, size=full} - Text copy: "You started <number-of-translations> translations some months ago. Consider publishing them before they get automatically discarded after a year." - Opening the main notification leads to the Translation dashboard showing the in-progress view. - Opening the individual notifications leads to the Translation editor for each translation.

When users have not been working on a translation for a while, a notification can help them to (a) continue the work, or (b) decide to publish the current content (avoid this knowledge to be lost). This is also useful as a warning for old drafts being automatically deleted (T183890), and preventing the issues of trying to continue a translation for which the original article has changed significatively. Considerations:# Proposed solution Send a notifications for translations that were started 3 months ago and have not been published by the user. If there are several translations in such situation, the notifications will be grouped into a bundle. These notifications are illustrated below: {F12261110, size=full} - Text copy: "Your started translating <page-name> some months ago. Consider publishing it before it gets automatically discarded after a year." - We want to notify about drafts without activity since last month (only sending one notification mentioning all pending)Main action (opening the notification): leads to the Translation editor for the translation. - Secondary action: “Your translations” leads to the Translations dashboard showing the in-progress view. **Bundled version** {F12261125, size=full} -- In the translation list we want to add a label marking those drafts. Text copy: "You started <number-of-translations> translations some months ago. Consider publishing them before they get automatically discarded after a year." - We want to consider only drafts for which- Opening the main notification leads to the corresponding article has not been publishedTranslation dashboard showing the in-progress view. -- We want to research how many drafts have an article that existed before the draft (this was a test by the user for CX: I'll try to translate "Paris"), after the draft (may have problems publishing), or went back to draft after publishing (users edited something). - This requires a background job to trigger the notifications Opening the individual notifications leads to the Translation editor for each translation.