Bugzilla

After the "Pre-Translation" setting gets enabled in the project admin, or after a new locale gets enables for a project with "Pre-Translation" setting enabled, a pre-translation background task gets triggered, which:

1. Identifies strings without any translations and any suggestions.
2. Engages TheAlgorithm (bug 1552796) to gather pre-translations.
3. Stores pre-translations as suggestions (approved=False) to DB.

The author should be set to a name like "Pontoon Translator <pontoon@mozilla.com>". Stats and Latest activity should be updated. Translations should NOT be stored in TM.

After:
- a "Pre-Translation" setting gets enabled in the project admin,
- a new locale gets enables for a project with "Pre-Translation" setting enabled,
- new strings are exposed for a project with "Pre-Translation" setting enabled,

a pre-translation background task gets triggered, which:
1. Identifies strings without any translations and any suggestions.
2. Engages TheAlgorithm (bug 1552796) to gather pre-translations.
3. Stores pre-translations as suggestions (approved=False) to DB.

The author should be set to a name like "Pontoon Translator <pontoon@mozilla.com>". Stats and Latest activity should be updated. Translations should NOT be stored in TM.

After:
- a "Pre-Translation" setting gets enabled in the project admin,
- a new locale gets enables for a project with "Pre-Translation" setting enabled,
- new strings are exposed for a project with "Pre-Translation" setting enabled,

a pre-translation background task gets triggered, which:
1. Identifies strings without any translations and any suggestions.
2. Engages TheAlgorithm (bug 1552796) to gather pre-translations.
3. Stores pre-translations as suggestions (approved=False) to DB.
3.1. Until pre-translations are stored as suggestions, we don't need to run checks on them.

The author should be set to a name like "Pontoon Translator <pontoon@mozilla.com>". Stats and Latest activity should be updated. Translations should NOT be stored in TM.