Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-7063

Announcement Banner on Customer portal after translated will remain even after removing the content from Announcement Banner

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 5.2.0
    • 4.11.0, 4.12.0, 4.13.1
    • Customer Portal

      Issue Summary

      Announcement Banner on Customer portal after translated will remain even after removing the content from Announcement Banner

      Steps to Reproduce

      1. Create a Service Desk Project
      2. Navigate to Project Settings --> Portal Settings --> Add a String Announcement Banner: "Welcome to IT Service Center"
      3. Navigate to Project Settings --> Language Support --> Add a language (Eg. Deutsch (Deutschland))
      4. On translation page, set the translation for Announcement Banner: "Willkommen im IT Service Center"
      5. Login as customer with Profile language set to Deutsch (Deutschland). Customer will see the Announcement Banner: "Willkommen im IT Service Center"
      6. As admin, Navigate to Project Settings --> Portal Settings --> and remove the Announcement Banner String.

      Expected Results

      The content on Announcement Banner should also be removed

      Actual Results

      The User with language Deutsch (Deutschland) will see the same content in the Announcement Banner as "Willkommen im IT Service Center"

      Workaround

      Before removing the content in Announcement Banner from Navigate to Project Settings --> Portal Settings --> "View and change your Customer Portal announcement". Remove the translated entry from
      Navigate to Project Settings --> Language Support --> Click on the selected Language --> Translation page --> Announcement Banner

            [JSDSERVER-7063] Announcement Banner on Customer portal after translated will remain even after removing the content from Announcement Banner

            James Lehmann added a comment -

            Quite interesting: a project translated system announcement has higher priority than the system announcement itself. 🤔

            I changed the system announcement several times and after a few seconds my change was undone. 

            I was able to fix the problem by changing the default language in the project twice.

            This requires that there is a second translation in the project (status green).

            1. To achieve this, I added the new announcement (EN) to my second, non-default, German translation.
            2. I changed the default language in my project to German
            3. I inserted the new announcement (EN) into the English translation.
            4. I checked the system announcements and updated them again (EN).
            5. I changed the default language in my project back to English.
            6. The German translation showed up the new announcement for translation.

            The system accepted the change. 😅

            @Atlassian: There's room for improvement, really. Customers should never be invited to make changes at DB level as described here. 🤫

             

            James Lehmann added a comment - Quite interesting: a project translated system announcement has higher priority than the system announcement itself. 🤔 I changed the system announcement several times and after a few seconds my change was undone.  I was able to fix the problem by changing the default language in the project twice. This requires that there is a second translation in the project (status green). To achieve this, I added the n ew announcement (EN ) to my second, non-default, German translation. I changed the default language in my project to German I inserted the new announcement (EN) into the English translation. I checked the system announcements and updated them again (EN) . I changed the default language in my project back to English. The German translation showed up the new announcement for translation. The system accepted the change. 😅 @Atlassian: There's room for improvement, really. Customers should never be invited to make changes at DB level as described here . 🤫  

            flaimo added a comment -

            Seems like attachments aren't allowed. Please see attachments in support ticket SDS-55428

            flaimo added a comment - Seems like attachments aren't allowed. Please see attachments in support ticket SDS-55428

            flaimo added a comment -

            The workaround only works for deleting the string for one language (german) but not for the other language (english (UK)).

            steps:
            1) do steps like described in your workaround
            2) project settings → customer natofications
            3) click "manage languages" in left sidepane
            4) click "set project default language"
            5) choose "german" and save
            6) click "language support" in left sidepane
            7) click on "english (uk)"

            → NOK: there is no way to delete the other translation. see screenshot. yet the banner shows up, when the user has set his interface language to "english (uk)". see second screenshot.

            flaimo added a comment - The workaround only works for deleting the string for one language (german) but not for the other language (english (UK)). steps: 1) do steps like described in your workaround 2) project settings → customer natofications 3) click "manage languages" in left sidepane 4) click "set project default language" 5) choose "german" and save 6) click "language support" in left sidepane 7) click on "english (uk)" → NOK: there is no way to delete the other translation. see screenshot. yet the banner shows up, when the user has set his interface language to "english (uk)". see second screenshot.

              cmarriott Charlie Marriott
              072fabfd41a3 Shreekesh Mohan
              Affected customers:
              11 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: