Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-8493

Add translation workflow to move updates in one space to a foreign language mirror

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Many users produce content in one language and need to maintain an up-to-date mirror of that content in another language. It would be useful to have a plugin that performs the following tasks

      • automatically adds the label 'for-translation' when a page is edited
      • add a new tab in Browse Space called 'Needs Translating' which lists all pages with the label 'needs-translating' and the last update date. Include a checkbox for each page plus 'Check All' to allows bulk marking as updated.

      Users will be able to mark a page as updated by deleting the for-translation label when viewing the page content. For themes that display a list of the page labels on the view tab, this only requires a doubleclick on the label delete. Users can use existing notification scheme to receive notifications when a page is labelled with 'needs-translating'.

      Use Case
      1) User A updates a Page A in the English space as normal
      2) User B is emailed is with page update notification, triggered by the label 'needs-translating' being added Page A
      3) User B views Page A in one window while they edit Page B, which is the translation of Page A, in another window. When Page B has been updated, they click the delete button for the 'needs-translating' label on Page A

      This is only one approach and attempts to use existing functionality as much as possible.

              Unassigned Unassigned
              david.soul@atlassian.com David Soul [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: