Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-73077

Better control for specific terms

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Problem Definition

      Confluence Cloud currently does not track or restrict specific terms that an organization might want to avoid, such as curse words or culturally inappropriate language.

      A few examples: "Whitelist/Blacklist", "Master/Slave", "Blackout", "Man Hours" etc.

      Suggested Solution

      Implement a new Feature to better control the usage of specific terms and suggest alternatives:

      1. Create a list of terms to be watched
      2. Provide a field for alternative terms to be suggested (Eg.: "Whitelist" can be changed to "Allowlist" instead)
      3. Automatically scan new content (create and update) for the listed terms (from Pages, Blog Posts, Questions, Calendar Events etc)
      4. Add Inline comments on top of the listed terms providing alternatives (Eg.: highlight a new "Whitelist" entry and add an Inline comment mentioning "Please consider using 'Allowlist' instead")
      5. Create a Job to scan existing content and search for the listed terms
      6. Provide a structured report based on the scanned results with metadata (Eg.: term used, number of times it is used, content where the term appears, link to the content, etc.)
      7. Create a banned terms list and avoid content to be saved if it contains any of those.

      Workaround

      1. Utilize third-party Apps / Plugins such as Datastorm Content Guard by Datastorm.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              tpallaro@atlassian.com Thiago Pallaro
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: